Management of EA
Authors: Wakar Khan and Saurabh Mittal, PhD
Enterprise Architecture maturity refers to the degree of formality and optimization of the EA program. An immature EA program may depend on ad hoc practices, weak governance and stakeholder engagement, and poor alignment to business needs. As EA programs mature, they may introduce formally defined steps, managed quality and outcome metrics, and active optimization of the processes. Although not guaranteed, enterprises that adopt mature EA practices are likely to operate efficiently and effectively, and to achieve desired business outcomes on a repeatable basis.
Maturity models offer structured levels that describe how the behaviors, practices and processes of an enterprise can be improved over time to increase EA maturity. Maturity models can also be used as a benchmark for comparison with other enterprises and as an aid to understanding how to make improvements. Cole (2016) defines five maturity levels:
- Level 1: Nonexistent – EA does not exist at this level
- Level 2: Reactive – EA need is recognized but EA practice is ad hoc and of response rather than a proactive approach
- Level 3: Functioning – EA is now operating and supporting the business. The foundational enterprise architect is well represented but is struggling to keep balance across the organization.
- Level 4: Integrated – EA is delivering consistent value as business outcomes
- Level 5: Ubiquitous – EA success has a trickle down effect across the organization and becomes a natural way of working.
The US Department of Commerce (DoC) developed an IT Architecture Capability Maturity Model (ACMM) to aid in conducting internal assessments. They have six levels: None, Initial, Under Development, Defined, Managed, Measured. The Initial and Under Development levels can be consolidated in the Reactive Level presented by Cole (2016).
Some case studies are also available in the Further Reading section.
- Cole, Z. (2016) Why Enterprise Architecture Needs Maturity Models. Erwin.
- TOGAF 8.1, Architecture Maturity Models.
- Muthu, S., Gilbert, S., (2017) Enterprise IT Architecture Assessment & Case Studies.
- Federal Enterprise Architecture Program Management Office, (n.d.) CBP Improves Efficiency and Effectiveness through EA, Enterprise Architecture (EA) in Action.
- Case Studies, Troux, Accessible at: https://success.planview.com/Troux/Resource_Center/Case_Studies
EABOK® Knowledge Areas
Organizational Scope and Structure of EA
Developing an EA
- Business Requirements and Value Proposition
- Methodologies and Processes
- Architecture Frameworks
- Data and Information Management
- Project Management
- Change Management
- Testing and Evaluation
- Modeling and Simulation
- Role of Reference Architectures
- How to Build a Reference Architecture
- Coordinating the Creation of a Reference Architecture
Management of EA
EA in Practice
Perspectives on EA
EABOK is an evolving knowledge base and more information will be released as available.
In addition to the EABOK Board members, the content is also contributed by the following MITRE employees:
- Carla Kendrick
- Brenda Yu
- Eddie Wang
- Rose Tykinski
- Wakar Khan
- Mike Russell
This website is managed by the EABOK Consortium and hosted by MITRE to enable stakeholder collaboration within the EA community.
EABOK and the EABOK logo are trademarks of MITRE and are used by The EABOK Consortium with permission.
All other trademarks are the property of their respective owners. All rights reserved.