Ücretsiz Kullanmaya Başla

Role Knowledge-Based Study

TOGAF · Enterprise Architecture Capability and Governance · Foundation · Architecture Board

Foundation topic explanations on Role.

Study notes

  1. Overview and Definition

    In the TOGAF Standard, 10th Edition, governance is a fundamental facet of managing and sustaining an Enterprise Architecture (EA) capability. At the center of enterprise architecture governance lies the Architecture Board.

    The Architecture Board is a formal group of stakeholders responsible for overseeing the implementation and evolution of the enterprise architecture. It represents the highest operational authority for architecture review, direction, and consistency across an enterprise.

    Primary Objectives

    The primary objectives of establishing an Architecture Board include:

    • Providing formal oversight and strategic direction for enterprise architecture initiatives.
    • Ensuring alignment between business strategy, business goals, and IT/architecture deliverables.
    • Enforcing consistency, quality, and reusability of architecture assets across organizational units.
    • Promoting architectural discipline, best practices, and compliance.

    Specific Roles within Governance

    The Architecture Board performs specific roles across the lifecycle of architecture definition and implementation:

    1. Architecture Contract and Compliance Review

    The board reviews architecture requests and project designs to verify compliance with documented enterprise architecture standards, principles, and reference models. It grants formal approval or mandates remediation when deviations occur.

    2. Dispensation Management

    When a project cannot comply with architectural standards due to valid business or technical constraints, the Architecture Board is the sole authority empowered to grant a formal dispensation (waiver). Dispensations are typically time-bound and require a defined remediation plan.

    3. Dispute Resolution and Arbitration

    When conflicting architectural viewpoints, competing business unit requirements, or technology trade-offs arise, the board acts as an impartial escalation and arbitration body.

    4. Maintenance of Architectural Integrity

    The board oversees updates to baseline standards, architecture principles, and the Architecture Repository, ensuring that additions and changes reflect strategic enterprise objectives rather than short-term project expedients.

    Distinguishing the Architecture Board from Other Bodies

    A common misconception in Enterprise Architecture governance is conflating the Architecture Board with operational or delivery-focused oversight bodies:

    • Architecture Board vs. Project Management Office (PMO): The PMO focuses on project execution metrics such as schedule, budget, resources, and scope management. Conversely, the Architecture Board focuses strictly on architectural compliance, coherence, quality, and strategic enterprise alignment.
    • Architecture Board vs. Change Advisory Board (CAB): A CAB operates primarily in the operational/IT service management domain (such as ITIL), assessing risk, scheduling, and rollback plans for live production changes. The Architecture Board governs architectural intent, target architectures, and standard compliance across development and deployment lifecycles.
    • Architecture Board vs. Executive Steering Committee: An executive steering committee holds ultimate funding and corporate prioritization authority, whereas the Architecture Board maintains technical and architectural stewardship across portfolios.

    Self-Assessment Scenario

    Consider the following situation to evaluate your understanding of the Architecture Board's role:

    Scenario: A strategic migration project identifies that a legacy subsystem cannot meet the enterprise's newly mandated data security reference architecture without a six-month delay and significant budget overruns. The project team seeks a temporary waiver to go live using the existing interface while developing compliant microservices in parallel.

    Which body holds the formal authority to evaluate and grant this waiver in TOGAF governance?

    1. Change Advisory Board (CAB): Evaluates operational rollout risks, but does not grant architectural dispensations.
    2. Project Management Office (PMO): Tracks schedule impact and costs, but lacks authority to approve architectural deviations.
    3. Architecture Board: Correct. The Architecture Board is explicitly tasked with evaluating compliance issues and issuing formal dispensations with clear terms.
    4. System Operations Team: Manages day-to-day infrastructure, without mandate over architectural principles or compliance.