Study guide
6.3 Phase G: Implementation Governance
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
6.3 Phase G: Implementation Governance
Key Takeaways Explain This Topic AI
Phase G objectives are to ensure conformance with the Target Architecture by implementation projects and to perform Architecture Governance functions for the solution and implementation-driven Change Requests.
Phase G steps include confirming deployment scope with development management, guiding solution deployment, performing compliance reviews, and conducting a post-implementation review.
Development organizations build the solution, while the architecture organization provides architectural oversight through Architecture Contracts and compliance reviews.
Phase G outputs include a signed Architecture Contract, Compliance Assessments, Change Requests, and architecture-compliant solutions deployed.
Dispensations for non-conforming work are granted for a given time period and set of operational parameters, after which compliance is re-assessed.
Last updated: September 2026
6.3 Phase G: Implementation Governance
Phase G provides an architectural oversight of the implementation . The Foundation syllabus asks you to briefly explain the purpose of Phase G and describe its objectives . Architecture Contracts and Architecture Compliance are covered in depth in Chapter 11; this section focuses on what Phase G does.
- Objectives of Phase G
- Ensure conformance with the Target Architecture by implementation projects
Perform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests
- Steps of Phase G
- Confirm Scope and Priorities for Deployment with Development Management
- Identify Deployment Resources and Skills
- Guide Development of Solutions Deployment
- Perform Enterprise Architecture Compliance Reviews
- Implement Business and IT Operations
- Perform Post-Implementation Review and Close the Implementation
Phase G brings together all the information needed for successful management of the implementation projects. The actual development is carried out by the development organization; the architecture organization provides architectural oversight , recommendations, and governance. TOGAF describes this in terms of establishing the implementation program and projects, deploying in phases according to the Implementation and Migration Plan, and making sure each implementation project is governed through an Architecture Contract and compliance reviews .
Inputs and Outputs
Key inputs Outputs
Implementation and Migration Plan; Implementation Governance Model (from Phase F) Architecture Contract (signed)
Architecture Definition Document; Architecture Requirements Specification; Architecture Roadmap; Transition Architectures Compliance Assessments
Request for Architecture Work identified during Phases E and F; Statement of Architecture Work; Architecture Vision Change Requests
Architecture Contract (standard); Architecture Governance Framework; Architecture Repository Architecture-compliant solutions deployed , including the implemented system, populated repository, compliance recommendations and dispensations, service delivery and performance recommendations, service level agreements, and post-implementation updates to the Architecture Vision and ADD
Architecture Contracts in Phase G
An Architecture Contract is a joint agreement between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture. TOGAF says Phase G establishes the connection between architecture and the implementation organization through the Architecture Contract. At the beginning of Phase G, a contract is agreed between the architecture function and the function implementing the architecture, typically the in-house systems development function or a major contractor. Within the step Guide Development of Solutions Deployment, the architects document the Architecture Contract and obtain signatures from all developing organizations and the sponsoring organization. See Section 11.3.
Compliance Reviews in Phase G
Architecture compliance reviews check implementation projects against the architecture at defined checkpoints. The outcome is recorded in a Compliance Assessment . When a project cannot comply, it can be remediated, or a dispensation can be granted through the governance process for a given time period and set of identified services and operational parameters, with the project re-assessed when it expires. TOGAF defines six levels of conformance, from Irrelevant to Non-conformant, covered in Section 11.4.
Change Requests During Implementation
Implementation often reveals issues — new technology, a supplier constraint, or a requirement that cannot be met. Phase G handles implementation-driven architecture Change Requests as part of its governance function. Depending on their impact, these are handled within Phase G, passed to Requirements Management, or sent to Phase H for architecture change management.
Architecture Governance vs. Project Management: Distinct Responsibilities
A frequent source of confusion is conflating architecture governance with project management or software engineering practices:
Dimension Implementation Governance (Phase G) Project Management (PMO / Scrum Master)
Primary Objective Safeguard architectural intent, standards compliance, and long-term enterprise coherence Deliver project scope within committed time, cost, and quality baselines
Primary Instrument Architecture Contracts, Compliance Reviews, Dispensations, Architecture Board Project Charters, Gantt Charts, Sprint Backlogs, Burndown Charts, Budgets
Level of Scrutiny Architectural boundaries, API standards, data schemas, security protocols, building block reuse Task completion, developer velocity, milestone dates, resource hours, sprint cadence
Authority Over Scope Can halt deployment or reject solutions for severe architectural non-conformance Manages scope trade-offs to meet delivery dates within contractual budget boundaries
Common Misunderstanding Phase G does not write code, debug software, or run daily developer standups Project managers do not grant architectural dispensations or redefine enterprise standards
Scenario: Governing a Claims Platform Rollout
An insurer's Phase F plan calls for three releases of a new claims platform. In Phase G the architects confirm deployment scope and priorities with the development manager, agree an Architecture Contract with the system integrator, and review the solution design at two checkpoints. At the second review, the integrator's reporting component uses an unapproved database. The Compliance Assessment records the issue; the Architecture Board grants a six-month dispensation because a regulatory deadline cannot move, with a condition that the component migrates to the standard platform in release three. After go-live, a post-implementation review records lessons learned and updates the Architecture Definition Document.
Common Exam Pitfalls
Thinking the architects build the solution. Development organizations implement; Phase G provides architectural oversight and governance.
Forgetting the second objective. Phase G also performs governance functions for implementation-driven Change Requests.
Confusing Phase G with Phase H. Phase G governs implementation; Phase H manages change to the architecture after it is in place.
Treating dispensations as permanent. Dispensations are granted for a given time period and set of parameters, and compliance is re-assessed.