We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.

Enterprise Architecture Matters

Adrian Grigoriu

What happens when the EA function does not produce an EA?

Vote 0 Votes

What happens when the EA function does not produce an EA  and it runs without an EA, without a blueprint...?

In the absence of the EA blueprint, the EA function can only run arbitrarily. And that's happening so often today.

EA work mainly validates solution architectures and technology investments against a few experienced IT minds. But there is no reference EA.

EA results depend on the EA architect skills as such. Too much so. The EA architect becomes the main risk, factor of success or lack of it.

The EA team, without an EA, does typically solution architecture reviews work and eventually IT roadmapping.

It does not coordinate the production of an EA against which solutions should be verified, technology should be selected, processes could be improved...

Thus EA team skills are thus  focused on general IT and knowledge of the enterprise and domain rather than architecture.

That is why so often EA is defined as a function alone, as a practice and governance rather than as an Enterprise blueprint and structure, in the first place. But EA requires both.

 And A Happy and Good New Year to You

 Adrian @ http://www.enterprise-architecture-matters.co.uk/home

1 Comment

| Leave a comment

Hello Adrian,

I agree with your statement: EA requires both a function /practice / governance AND blueprint and structure.

Way too often people focus only on one part and skip the others, which leads to an imbalance situation. This imbalance can lead the whole architecture approach to fail, since like I am using to say: "Doing architecture to do architecture is useless..." We always have to come back to what are the objectives of such approach and having blueprint is fundamental to keep track of what is producing through projects (knowledge management) and to control these developments (to perform tests, KPIs...)

Wish you a happy new year too.

Leave a comment

Adrian Grigoriu blogs about everything relating to enterprise and business architecture, SOA, frameworks, design, planning, execution, organization and related issues.

Adrian Grigoriu

Adrian is an executive consultant in enterprise architecture, former head of enterprise architecture at Ofcom, the spectrum and broadcasting U.K. regulatory agency and chief architect at TM Forum, an organization providing a reference integrated business architecture framework, best practices and standards for the telecommunications and digital media industries. He also was a high technology, enterprise architecture and strategy senior manager at Accenture and Vodafone, and a principal consultant and lead architect at Qantas, Logica, Lucent Bell Labs and Nokia. He is the author of two books on enterprise architecture development available on Kindle and published articles with BPTrends, the Microsoft Architecture Journal and the EI magazine. Shortlisted by Computer Weekly for the IT Industry blogger of the year 2011.

Recently Commented On

Monthly Archives