There are so many details in IT Application implementations
that many EA Teams do not have the time to be involved with. This is a
critique, not a criticism. Many decisions are made “on the fly” by the
functional lead along with consensus by the rest of the group but this can be
problematic. Quickly made decisions lead to quick action but that does not mean
the time has been taken to evaluate the appropriate viewpoints. To truly
address this, a cadence needs to be established that bridges the various constituencies,
with a “just enough, just in time” approach. Phasing meetings throughout
iterations of a project consistency in the exchange and evaluation of ideas
from multiple levels of an organization. This includes regularly scheduled
feedback loops through which EA team members can act as gatekeepers for the
local project level decisions.
Additionally, the stratification of each meeting should
scale across meetings so that non-pertinant stakeholders are not involved in
discussions that don’t require their input. Being respectful of each and every
parties time, large and small, will win a project manager’s favor. The
establishment of that trust can be a foundation that the EA team builds with a
vendor concurrent with the implementation. A project manager is a relationship
builder and E A teams should take the time to integrate EA tasks into their actives.
Indeed. There lies somewhere in between trying to account for every contingency (impossible!) and making decisions at random. That's why I love Agile project management. By reducing the project down to discrete portions, it is much easier to make changes if the product isn't meeting customer requirements. And that's huge. Why waste time and resources building something that no one even wants?!
ReplyDelete