Rants
Questions
Soapbox
Best Practices
Apply today for a FREE subscription to CIO Magazine!
Thu, Oct 29, 2009 11:00 EDT
|
Posted by: grigoriu in Soapbox Topic: Architecture
Current Rating: |
To become relevant to the entire Enterprise and deliver to expectations, EA has to be elevated at a level where it can correlate and coordinate all relevant activities of an Enterprise such as business strategy alignment, BPM, xSigma, organization design, non-IT technology, IT... all traditionally performed by the non-IT communities. If you cannot beat them, work with them.
Currently, EA does not take advantage of the work performed by BPM, quality, strategy... teams. The teams ignore each other acting as in silos. Then EA would have to perform these activities in its own program because processes for instance or strategy alignment are part of the business/EA architecture mission, I think you agree. But this would generate never ending duplications, costs, politics...
In the end, it is either (1) work with them, (2) duplicate these business activities or (3) reduce the EA scope to IT as it happens now. After all, there is an explanation for that.
Simple synchronization between activities may do for the beginning but in the end, someone has to orchestrate, to lead. The Chief EA architect does not necessarily have to come from the today's EA IT ranks. It will have to be a new breed.
EA would not succeed unless it becomes a coordinated effort!
http://it.toolbox.com/blogs/ea-matters/