Developing an EA
Author: Carla D. Kendrick, PhD
Organizations are complex systems and using enterprise architecture to reflect and represent these systems is not a simple undertaking. Developing, maintaining and sustaining EA requires both planning and management. Therefore, a competency in project management is needed by EA practitioners. Using a formalized project management approach with well-defined steps, clearly defined deliverables, and regular checkpoints (also referred as “gates”) is essential. Good project management also includes implementing metrics to assess performance and determine if deliverables align with organizational goals and objectives. Metrics should also determine if deliverables are meeting the needs of stakeholders. The project management methodology should also link EA with business and IT efforts. Business linkage ensures that the EA effort is effectively translating business goals into project goals. The architecture linkage ensures standards and IT design decisions/governance reflect overall “enterprise” needs. The EA project manager may also find it necessary to serve as the intermediary/negotiator between business and IT. A worthwhile goal is for these linkages to become habitual behavior within an organization.
The Project Management Institute (PMI) defines project management as the “application of knowledge, skills, tools, and techniques to project activities to meet the project requirements.” A basic project management activity is the development of a project plan, and EA projects are no exception. A project plan is a formal document and should receive approval from senior management. Typical topics covered in the plan are: scope, key roles and responsibilities, milestones, deliverables, objectives, governance and metrics. Communicating and setting expectations for the EA effort are also important activities for the EA project manager.
- Project Management Institute (2018). What is Project Management.
- Ross, J.W., Weill, P. and Robertson, D.C. (2006). Enterprise Architecture as Strategy. Boston, MA: Harvard Business School Publishing.
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.