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

Enterprise Architecture Governance

user-pic
Vote 0 Votes
The EA team alone cannot develop and maintain the whole EA without participation of stakeholders with respect to their own parts, 

Hence, the EA group has to create a governance framework that would be employed in the consistent design of EA artifacts, solution architectures and in the decision making process,  

Governance is essential if properly constructed. Once created, it has to be conformed with. 
Still, problems appear when "projects shall obey the decisions by the EA group alone. 

The governance, by definition, should act through principles, control checkpoints in the project phases, good definition of who makes what decisions, roadmaps, strategies... all widely agreed beforehand rather than appearing like instant diktats from a body like EA which should only act by exception, unlike today. 
In the case of IT, which maybe your case, the EA might play the role of the governing body but be balanced by the presence of solutions architects, IT management...

One has to make sure that governance has input and meets the approval of all concerned parts. Governance should be approved by a more encompassing and different body from EA where project architects and many other stakeholders may have a say. 

Then, projects and activities should all submit to the governaning rules and body, which body may not necessarily be the EA group but may have participation from. 
There may be exceptions for some works. Governance may be constantly reviewed and updated, if necessary.

Governance reduces chaos. Governance avoids friction. Governance enforcesw consistency and predictable results.

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

Blogs

ADVERTISEMENT