Never the twain shall meet?
James (2006) in the Gartner article titled "Making Technology Standards Work" analyzes the lament put forth by Enterprise Architects that technology standards defined are ignored.
Although the disadvantages of a diverse and complex technology portfolio are obvious to the
architects that try to contain it, in many instances the standards that they attempt to apply are
ignored, and they fail to change the way that projects work (James, 2006, p. 2).
The different perspective of the project team by the very nature of the work which has a tunnel vision is the explanation provided by James. The article recommends a key element of linking architecture with business benefits to counter this. This link would then provide the relevant context for the architecture and lets trade-offs be made between the benefits of architecture standards and the granting of standards waivers to projects. The article also points out the ways architects can make this connection effective.
This week's class readings had a thread on the importance of architecture having a connection to the projects on the ground. Failure would probably mean pie in the sky as far as attaining EA maturity.
References
James, A.G. (2006, February). Making technology standards work. Gartner id G00137199.
No comments:
Post a Comment