Introduction Knowledge-Based Study

Study notes

1. An Enterprise Architecture (EA) Capability represents the collective ability, resources, organizational structures, and practices required for an enterprise to initiate, conduct, and sustain enterprise architecture over time. In the TOGAF Standard, 10th Edition, establishing an architecture capability is not treated as a one-time project, but as an ongoing business function aligned with corporate goals.

   Key elements that constitute an EA Capability include:

   • People and Skills: Roles, competencies, and talent development necessary to develop and evaluate architectures.
   • Processes and Methods: Documented, repeatable architecture methods—principally driven by the TOGAF Architecture Development Method (ADM).
   • Tools and Repository: Repositories and modeling tools that manage architecture deliverables, artifacts, and building blocks.
   • Governance Framework: Clear accountability mechanisms ensuring alignment with business strategy and compliance.

   Architecture Governance is the practice by which enterprise architectures and other capabilities are managed and controlled at an enterprise-wide level. It sits within the broader hierarchy of organizational governance.

   The standard distinguishes architecture governance from adjacent governance disciplines:

   • Corporate Governance: Directs and controls the broader commercial, legal, and operational activities of the business.
   • Technology / IT Governance: Focuses specifically on IT investments, operational service management, and technology performance.
   • Architecture Governance: Ensures that business and technology transformations conform to agreed enterprise architecture standards, principles, and strategic target states.

   Without effective governance, an architecture practice risks producing conceptual models that fail to influence actual operational and implementation decisions.

   Setting up and maintaining an EA Capability interacts continuously with the TOGAF ADM:

   • The Preliminary Phase: Focuses on defining the enterprise context, determining the scope of the capability, establishing architecture principles, and tailoring the framework to fit the organization.
   • Phase G (Implementation Governance): Directs architecture reviews to verify that implementation projects comply with the Target Architecture.
   • Phase H (Architecture Change Management): Ensures that the architecture capability adapts systematically to changes in enterprise strategy and technology advancements.

   Consequently, an effective EA Capability functions as both a producer of strategic direction and an evaluator of change initiatives.

   Core Conceptual Distinction

   A common misconception is conflating Architecture Governance with Project Management Governance. Project governance controls cost, schedule, and immediate project deliverables. Architecture governance evaluates whether project outcomes adhere to long-term enterprise goals and standard architecture building blocks.

   ---

   Practice Knowledge Check

   Question: Which statement most accurately defines the primary purpose of establishing an Enterprise Architecture Capability according to the TOGAF Standard?

   1. To enforce rigid IT procurement policies that eliminate all vendor diversification.
   2. To provide an ongoing organizational capacity, structure, and governance model to direct and sustain architectural change.
   3. To replace corporate governance boards with an independent enterprise architecture steering committee.
   4. To execute an isolated, one-off IT documentation initiative for legacy applications.

   Correct Answer: 2

   Explanation: An EA Capability is an ongoing organizational capability—incorporating people, skills, governance, and processes—designed to sustain continuous architectural direction and transformation. It does not replace corporate governance, nor is it a temporary documentation exercise or a simple procurement control mechanism.