Thanks for the repost. Just wanted to correct the spelling of my name - it is David Baker, not Barker.
Thanks again,
Dave Baker
Chief Architect
Diamond Management & Technology Consultants
twitter: davidcbaker
Enterprise architects are the bridge between business and IT, and are expected to speak both languages. So they’re in a good position to turn IT projects into gold. But this doesn’t happen automatically — so Chris Curran and David Barker posted some advice on how to boost EA’s value as a resource to the business, in four easy steps:
- Launch (or re-launch) ‘project architecture assistance services’: The role of EA is to “make a a positive impact on the delivery of the new business capabilities (e.g. improved speed to market, improved reliability, etc).”
- Blueprint a high-priority business domain: “IT knows it is working on the right projects to deliver the greatest business value. The most tangible value, however, is through delivery of the projects identified by the blueprint.”
- Develop an enterprise “core” blueprint: A high-level enterprise-wide blueprint can help identify “the core IT functions that serve as many business units as possible.”
- Develop a blueprint for one or more core IT capabilities: The EA team is in a position to understand and help identify a handful of core IT services such as master data, data management, application integration, portal platforms, or B2B integration.
