Study guide
11.2 The Architecture Board
TOGAF Enterprise Architecture Foundation OGEA-101
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Enterprise Architecture & the TOGAF Standard
1.1 The Enterprise, the Purpose of EA & Its Benefits 1.2 Why the TOGAF Standard: Framework, Documentation Set & Certification 1.3 The Four Architecture Domains & Architecture Abstraction
2 Chapter 2: Enterprise Continuum, Architecture Repository, Content Framework & Capability
2.1 The Enterprise Continuum 2.2 The Architecture Repository 2.3 The TOGAF Content Framework & Enterprise Metamodel 2.4 Architecture Capability
3 Chapter 3: Key TOGAF Terminology
3.1 Terms for Architecture Domains, Levels, States & Capability 3.2 Terms for Work Products, Models, Requirements & Change
4 Chapter 4: ADM Fundamentals, Preliminary Phase & Phase A
4.1 The ADM Cycle, Its Phases & Information Flow 4.2 Draft vs. Approved Deliverables & the Iterative ADM 4.3 Governing EA, Scoping the Architecture & Alternatives 4.4 The Preliminary Phase 4.5 Phase A: Architecture Vision
5 Chapter 5: Architecture Definition — Phases B, C & D
5.1 Phase B: Business Architecture 5.2 Phase C: Information Systems Architectures — Data & Application 5.3 Phase D: Technology Architecture
6 Chapter 6: Opportunities, Migration Planning & Implementation Governance (Phases E, F & G)
6.1 Phase E: Opportunities & Solutions 6.2 Phase F: Migration Planning 6.3 Phase G: Implementation Governance
7 Chapter 7: Phase H, Requirements Management & Agile Delivery
7.1 Phase H: Architecture Change Management 7.2 Requirements Management 7.3 Supporting Agile Software Development with the ADM
8 Chapter 8: ADM Techniques I — Guidelines, Principles, Business Scenarios & Gap Analysis
8.1 ADM Guidelines & Techniques and Architecture Principles 8.2 Business Scenarios 8.3 Gap Analysis
9 Chapter 9: ADM Techniques II — Interoperability, Transformation Readiness & Risk
9.1 Interoperability 9.2 Business Transformation Readiness Assessment 9.3 Risk Management
10 Chapter 10: Applying the ADM
10.1 Guidance for Applying TOGAF, Iteration & Concurrent Phases 10.2 The Architecture Landscape: Strategic, Segment & Capability Levels 10.3 Architecture Partitioning 10.4 The Four Purposes of Architecture 10.5 Applying the TOGAF Standard in the Digital Enterprise
11 Chapter 11: Architecture Governance
11.1 Architecture Governance: Concept & Benefits 11.2 The Architecture Board 11.3 Architecture Contracts 11.4 Architecture Compliance
12 Chapter 12: Architecture Content
12.1 Stakeholders, Concerns, Views & Viewpoints 12.2 Building Blocks: ABBs & SBBs 12.3 ADM Deliverables I: Preliminary Phase and Architecture Vision 12.4 ADM Deliverables II: From Architecture Definition to Change
11.2 The Architecture Board
Key Takeaways Explain This Topic AI
A cross-organization Architecture Board is a key element of a successful architecture governance strategy, overseeing its implementation.
Architecture Board goals include consistency between sub-architectures, identifying re-usable components, and enforcement of Architecture Compliance.
The Architecture Board supports a visible escalation capability for out-of-bounds decisions.
The Architecture Board identifies divergence from Architecture Contracts and plans realignment through dispensations or policy updates.
TOGAF suggests an Architecture Board of four or five permanent members, and no more than ten.
Last updated: September 2026
11.2 The Architecture Board
The Foundation syllabus asks you to briefly explain the role of an Architecture Board and its responsibilities . A key element in a successful architecture governance strategy is a cross-organization Architecture Board to oversee the implementation of that strategy.
Role of the Architecture Board
The Architecture Board is an executive-level body, representative of all the key stakeholders in the architecture, that is typically responsible for the review and maintenance of the overall architecture. It oversees the implementation of the architecture governance strategy and provides the mechanism through which architecture decisions are made visible, agreed, and enforced.
Why Organizations Set One Up
Typical triggers for establishing an Architecture Board include:
- A new CIO
- Merger or acquisition
- Organizational restructuring
- Consideration of a move to newer forms of computing
- Recognition that IT is poorly aligned to the business
- The desire to achieve competitive advantage through technology
- Creation of an enterprise architecture program
- Significant business change or rapid growth
- Requirement for complex, cross-functional solutions
- Responsibilities
The Architecture Board is typically made responsible, and accountable, for achieving some or all of these goals:
- Goal What it means in practice
- Consistency between sub-architectures Architectures developed by different teams or partitions fit together
- Identifying re-usable components Components are recognized and promoted for re-use
Flexibility of Enterprise Architecture The architecture can meet changing business needs and leverage new technologies
Enforcement of Architecture Compliance Projects comply with the architecture
Improving the maturity level of architecture discipline The organization's architecture practice improves over time
- Ensuring architecture-based development is adopted Architecture is used to guide development, not bypassed
- Supporting a visible escalation capability There is a clear route for out-of-bounds decisions
From an operational perspective, the Board is also responsible for:
- Monitoring and control of architecture compliance activities
- Providing the basis for all decision-making with regard to the architectures
Providing a mechanism for the formal acceptance and approval of architecture through consensus and authorized publication
Providing a fundamental control mechanism for ensuring effective implementation of the architecture
Establishing and maintaining the link between implementation of the architecture, the architectural strategy and objectives, and the strategic objectives of the business
Identifying divergence from the Architecture Contract and planning activities to realign with it, through dispensations or policy updates
Resolving ambiguities, issues, or conflicts that have been escalated, and providing advice, guidance, and information
Setting Up and Operating the Board
- Aspect TOGAF guidance
- Membership Representative of all the key stakeholders; executive-level and cross-organizational
- Size A good rule of thumb is four or five permanent members, and no more than ten
Rotation To keep the Board manageable yet representative, consider rotating membership , giving decision-makers across the enterprise exposure over time
Charter The Board's responsibilities and authority should be defined and agreed
Meetings and records Meetings follow an agenda, and decisions, including compliance assessments and dispensations, are recorded so they can be audited
The Architecture Board Across the ADM
Where Board involvement
Preliminary Phase The architecture governance framework, including the Board's role, is confirmed; Architecture Principles are agreed with key stakeholders such as the Board
Requirements Management The Architecture Requirements Repository holds the authorized architecture requirements agreed with the Architecture Board
Phase G Compliance assessments, divergence from Architecture Contracts, and dispensations come to the Board
Phase H The step "Manage Governance Process" arranges a meeting of the Architecture Board, or other governing council, to decide on handling changes, including technology and business changes and dispensations
Partitioned architectures The Board maintains consistency between sub-architectures developed by different teams
Because the Board sees decisions across projects and partitions, it is also well placed to spot re-usable components and to drive improvement in the maturity of the architecture discipline.
Scenario: Escalating an Out-of-Bounds Decision
Two business units propose competing customer relationship management platforms. Neither project team has the authority to decide for the enterprise, so the issue is escalated to the Architecture Board. Using the architecture principles ("Common Use Applications"), the strategic architecture, and the re-use goal, the Board selects one platform as the enterprise standard, records the decision, and plans how the second unit will migrate — consistency between sub-architectures, re-use, and a visible escalation route all at work.
Common Exam Pitfalls
Treating the Board as a project management office. It governs architecture decisions and compliance; it does not run project schedules.
Making the Board too large. TOGAF suggests four or five permanent members and no more than ten.
Forgetting consistency between sub-architectures. It is a core Board responsibility, especially with partitioned architectures.
Overlooking escalation. Supporting a visible escalation capability for out-of-bounds decisions is an explicit goal.