Study guide
10.1 Phase G Objectives, Implementation Governance Structure, and Project Architecture Hand-off
TOGAF Enterprise Architecture Practitioner OGEA-103
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Mechanics & Foundation Overview
1.1 OGEA-103 Exam Structure, Gradient Scoring & Open-Book Strategy 1.2 The TOGAF Standard 10th Edition Structure & Core Concepts 1.3 Enterprise Architecture in Practice: Context, Scope, and Architecture Domains 1.4 The Context for Enterprise Architecture: Purpose, Capability, Security, and the Digital Enterprise
2 Chapter 2: Preliminary Phase & Establishing the EA Capability
2.1 Preliminary Phase Objectives, Inputs, and Activities 2.2 Scope of the Enterprise and Defining the Architecture Footprint 2.3 Establishing Architecture Governance, Frameworks, and Tools
3 Chapter 3: Architecture Vision & Stakeholder Management (Phase A)
3.1 Phase A Objectives, Request for Architecture Work, and Scope Definition 3.2 Stakeholder Management: Identification, Classification, the Power/Interest Grid, and the Stakeholder Map 3.3 Business Scenarios Technique for Problem Definition and Requirements Elicitation 3.4 Architecture Vision, Communications Plan, and Statement of Architecture Work Approval
4 Chapter 4: Business Architecture (Phase B)
4.1 Phase B Objectives, Steps, and Business Modeling Approaches 4.2 Business Capabilities, Capability Mapping, and Assessment 4.3 Value Streams, Value Stream Mapping, and Capability Cross-Mapping 4.4 Business Architecture Artifacts, Gap Analysis, and Architecture Definition Document Updates
5 Chapter 5: Information Systems Architectures — Data Architecture (Phase C)
5.1 Phase C Data Architecture Objectives, Approach, and Data Principles 5.2 Conceptual, Logical, and Physical Data Models and Data Management 5.3 Data Entity/Business Function Matrix, Data Architecture Gap Analysis, and Interoperability Requirements
6 Chapter 6: Information Systems Architectures — Application Architecture (Phase C)
6.1 Phase C Application Architecture Objectives, Approach, and Baseline vs. Target First 6.2 Application Portfolio Rationalization, Component Modeling, and Application Integration 6.3 Application/Organization Matrix, Application Gap Analysis, and Boundary Definitions
7 Chapter 7: Technology Architecture (Phase D)
7.1 Phase D Objectives, Cloud & Modern Platforms, and Technology Principles 7.2 Technology Standards, the Standards Library, Platform Services, and Infrastructure Modeling 7.3 Technology Gap Analysis, Non-Functional Requirements, and Reference Models
8 Chapter 8: Opportunities and Solutions (Phase E)
8.1 Phase E Objectives, Consolidated Gap Analysis, and Work Package Formulation 8.2 Architecture Building Blocks (ABBs) to Solution Building Blocks (SBBs) Transition 8.3 Transition Architectures, Incremental Delivery, and Dependency Analysis 8.4 Architecture Roadmap Development and Trade-Off Analysis 8.5 Business Transformation Readiness Assessment and Risk Management
9 Chapter 9: Migration Planning (Phase F)
9.1 Phase F Objectives, Stakeholder Collaboration, and Governance Alignment 9.2 Business Value Assessment, Cost-Benefit Analysis, and Risk/Feasibility Scoring 9.3 Implementation and Migration Plan Deliverable, Resource Allocation, and Transition Roadmaps
10 Chapter 10: Implementation Governance (Phase G)
10.1 Phase G Objectives, Implementation Governance Structure, and Project Architecture Hand-off 10.2 Architecture Contracts: Purpose, Types, Timing, and Stakeholder Commitments 10.3 Architecture Compliance Reviews: Conformance Levels, Process, Timing, and Checklists
11 Chapter 11: Architecture Change Management (Phase H) & Requirements Management
11.1 Phase H Objectives, Drivers of Architecture Change, and Value Monitoring 11.2 Change Classification: Simplification, Incremental, and Re-Architecting Changes 11.3 Ongoing Governance, Retirement of Solutions, and Maintenance vs. New ADM Cycle 11.4 Requirements Management: Central Role, Traceability, Mid-Phase Discovery, and Scope Conflict
12 Chapter 12: Architecture Governance, Boards, and Dispensations
12.1 Architecture Governance Framework, Organizational Roles, and RACI Matrix 12.2 Architecture Board Structure, Federation, Responsibilities, and Meeting Operations 12.3 Compliance Assessment, Dispensation Process, Expiration, and Remediation Tracking 12.4 Architecture Principles, the Decision Log, and Resolving Principle Conflicts
13 Chapter 13: Architecture Content Framework & Architecture Repository
13.1 The TOGAF Content Framework and Enterprise Metamodel 13.2 Deliverables, Artifacts (Catalogs, Matrices, Diagrams), and Building Blocks (ABBs vs SBBs) 13.3 Architectural Views, Viewpoints, Stakeholder Concerns, and ISO/IEC/IEEE 42010 13.4 The Enterprise Continuum and the TOGAF 10 Architecture Repository
14 Chapter 14: EA Capability, Tailoring, and Iteration
14.1 Tailoring the ADM: Enterprise Context, Process Weight, and Agile Integration 14.2 ADM Iteration Cycles, Levels, and Classes of Architecture Engagement 14.3 Architecture Maturity Models, Capability Assessment, and EA Performance Measures 14.4 Supporting the ADM Work: The TOGAF Library, Series Guides, Patterns, and Security
10.1 Phase G Objectives, Implementation Governance Structure, and Project Architecture Hand-off
Key Takeaways Explain This Topic AI
Phase G has two objectives: ensure conformance with the Target Architecture by implementation projects, and perform appropriate Architecture Governance functions for the solution and any implementation-driven Change Requests.
Phase G's third step, Guide development of solutions deployment, documents the Architecture Contract and obtains signatures from all developing organizations and the sponsoring organization.
Architects govern architectural conformance, interfaces, and standards, while project managers and delivery leads own schedules, task allocation, and resourcing.
Unexpected constraints found during implementation go through formal governance (Change Requests or dispensations) rather than undocumented workarounds.
Phase G outputs include the signed Architecture Contract, Compliance Assessments, Change Requests, and architecture-compliant solutions, with new baselines published to the Architecture Repository.
Last updated: October 2026
10.1 Phase G Objectives, Implementation Governance Structure, and Project Architecture Hand-off
Phase G of the TOGAF Architecture Development Method (ADM) marks the decisive transition where strategic architecture definitions materialize into operational reality. Throughout earlier phases of the ADM, enterprise architects define the baseline and target states across Business, Data, Application, and Technology domains (Phases B through D), evaluate candidate solution building blocks (Phase E), and establish a prioritized implementation roadmap with committed funding (Phase F). However, even the most rigorously designed target architecture remains an unfulfilled conceptual exercise if real-world engineering teams deviate from architectural standards during implementation. Phase G provides the continuous, formal oversight required to guide solution delivery, protect architectural integrity, and ensure the enterprise realizes its intended business value.
Objectives and Steps of Phase G
The TOGAF Standard, 10th Edition states two objectives for 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.
Its six steps are:
Confirm scope and priorities for deployment with development management : review migration planning outputs, identify EA priorities for development teams, identify deployment issues, identify building blocks for replacement or update, and perform gap analysis on the Enterprise Architecture and solutions framework.
Identify deployment resources and skills , including the system development methods to be used and how they will feed design information back to the architecture team.
Guide development of solutions deployment : formulate a recommendation for each implementation project (scope, strategic requirements, Change Requests, rules for conformance, and timeline requirements, documented in an impact analysis); document the Architecture Contract and obtain signatures from all developing organizations and the sponsoring organization ; update the Enterprise Continuum directory and repository for solutions; guide business and IT operating models and operational requirements; and produce the Implementation Plan.
Perform Enterprise Architecture Compliance reviews of ongoing implementation governance and each building block, conduct post-development reviews, and close the development part of deployment projects.
Implement business and IT operations , including publishing new Baseline Architectures to the Architecture Repository.
Perform post-implementation review and close the implementation.
TOGAF notes that an organization-specific development process runs in parallel with Phase G, and that the favored approach deploys the target as a series of transitions, each delivering business benefit in its own right.
Establishing Governance Over Concurrent Implementation Projects
In modern enterprises, an architectural roadmap is rarely executed by a single, monolithic delivery team. Instead, transformations unfold across dozens of concurrent, asynchronous projects, programs, agile release trains, and third-party vendor work streams. Phase G establishes a multi-tiered governance structure designed to maintain enterprise coherence while enabling delivery velocity.
The Multi-Tiered Implementation Governance Model
To balance enterprise coherence with project autonomy, the implementation governance structure operates across three distinct levels:
Enterprise Architecture Board (Strategic Governance) : Serves as the ultimate cross-domain governance authority. The Architecture Board approves Architecture Contracts, adjudicates cross-project dependency conflicts, and evaluates formal requests for dispensations or architectural change.
Project Steering Committees & Domain Architects (Tactical Governance) : Bridges the enterprise roadmap with individual project charters. Domain architects (Business, Data, Application, and Infrastructure) attend project stage gates, review solution designs, and evaluate integration touchpoints.
Solution Delivery Teams & Agile Squads (Operational Execution) : Consists of software engineers, systems integrators, cloud architects, and Scrum teams responsible for physical construction, automated testing, and deployment.
RACI Division of Governance Responsibilities
A classic pitfall on the OGEA-103 examination involves confusing the responsibilities of the enterprise architect with those of the project manager. The TOGAF Standard enforces a clean boundary: architects govern architectural integrity, standards conformance, and interface specifications , while project managers govern delivery schedules, task work breakdown structures, budgets, and operational resource assignments .
Implementation Activity Enterprise Architect (EA) Solution Architect (SA) Project Manager (PMO) Development Lead / Agile Team
- Establish Architecture Contracts Accountable Consulted Responsible Informed
- Define Work Breakdown Structure (WBS) Informed Consulted Accountable Responsible
- Daily Task Allocation & Sprint Scheduling Informed Informed Accountable Responsible
- System Detailed Design (SBB Level) Consulted Accountable Informed Responsible
- Architecture Compliance Reviews Accountable Responsible Consulted Informed
- Change Request Evaluation (Architectural) Accountable Responsible Consulted Informed
- Operational Defect Triage (Code-Level) Informed Consulted Responsible Accountable
- The Project Architecture Hand-Off Mechanism
The transition from migration planning (Phase F) to implementation governance (Phase G) requires a formal project architecture hand-off. The hand-off is not an abrupt "throw it over the wall" event where enterprise architects hand over static documentation and disappear. Rather, it is a structured, collaborative briefing and operationalization process.
Key Components of the Hand-Off
Translating ABBs to SBBs : Enterprise architects guide solution architects in translating conceptual Architecture Building Blocks (ABBs) defined in earlier phases into concrete, vendor-specific Solution Building Blocks (SBBs), commercial off-the-shelf (COTS) packages, or open-source frameworks.
Communicating Constraints and Principles : Delivery teams are briefed on non-negotiable architectural principles, cybersecurity baselines, data sovereignty laws, latency budgets, and interoperability mandates.
Establishing Compliance Stage Gates : The architecture team and PMO agree on mandatory compliance review gates (typically aligned with design sign-off, mid-build verification, and pre-go-live readiness).
Bridging Enterprise Architecture with Agile and DevOps Delivery
Modern enterprises frequently implement architecture through agile delivery frameworks (e.g., Scrum, SAFe, Spotify model). Enterprise architects bridge the gap with agile delivery through three collaborative mechanisms:
Architectural Runway : Enterprise architects provide technical enablers, shared infrastructure, and foundational APIs ahead of user-facing sprint cycles, ensuring teams do not hit architectural dead ends.
Enabler User Stories and Guardrails : High-level architectural requirements are decomposed into enabler user stories, non-functional requirements (NFRs), and architectural guardrails within the team's product backlog.
Definition of Done (DoD) Integration : Architecture compliance criteria—such as automated static security scans, API schema validation, and logging standards—are embedded directly into the team's Definition of Done and automated CI/CD deployment pipelines.
Managing Technical Constraints and Discoveries During Implementation
Even the most rigorous enterprise architecture cannot anticipate every physical constraint encountered during low-level engineering. When implementation teams begin writing code, integrating legacy systems, or configuring cloud infrastructure, they frequently discover undocumented legacy behaviors, network throughput ceilings, or vendor software limitations.
The Governance Pathway: Local Adjustment vs. Formal Change Request
When unexpected technical realities emerge, Phase G provides two distinct handling mechanisms based on the severity of the deviation:
Local Implementation Tuning (Within Contract Tolerances) : If an issue can be resolved using alternative Solution Building Blocks that adhere fully to the existing Architecture Contract, enterprise standards, and interface schemas, the solution architect approves the adjustment locally without escalating to the Architecture Board.
Architectural Deviation (Breaching Contract Boundaries) : If resolving the constraint requires modifying external interfaces, introducing non-standard technologies, violating security policies, or delaying downstream work packages, the project cannot implement an ad-hoc workaround. The solution architect and project manager must submit a formal Change Request (CR) to the Architecture Board.
Preventing Architectural Erosion and Rogue Workarounds
A critical failure mode in enterprise implementations is the proliferation of undocumented, quick-and-dirty "code arounds" implemented under deadline pressure. These workarounds accumulate crippling technical debt, compromise cybersecurity posture, and break cross-system interoperability. Phase G governance ensures that all trade-offs are explicitly evaluated by the Architecture Board, resulting in an approved architecture update, a time-limited dispensation, or a mandated engineering redesign.
Phase G Inputs and Outputs
Knowing the inputs and outputs of Phase G is essential for the OGEA-103 examination:
Phase G Inputs Phase G Outputs
Implementation and Migration Plan : Baseline delivery schedule, work packages, and resource allocations from Phase F Architecture Contracts : Agreed, signed, and operationalized contracts binding delivery partners and business units
Architecture Definition Document (ADD) : Comprehensive specification of baseline, target, and intermediate Transition Architectures Compliance Assessments : Formal reports evaluating implementation artifacts against architecture specifications
Architecture Requirements Specification (ARS) : Non-functional requirements, technical constraints, and gap definitions Change Requests : Formally submitted requests for architecture modifications resulting from implementation constraints
Statement of Architecture Work : Scope, deliverables, and governance boundaries established in Phase A Architecture Updates : Updated ADD and ARS reflecting approved variances, as-built designs, and SBB catalog entries
Transition Architectures : Staged capability targets to verify during incremental deployments Deployed Solution Building Blocks : Operational systems handed over to IT service management operations
Common Exam Traps & Anti-patterns
The 'Architect as Project Manager' Anti-Pattern : Exam questions frequently tempt candidates with options where an enterprise architect steps in to manage daily developer sprint points, assign Jira tasks, or redraw Gantt charts. This is an incorrect distracter. Architects govern architectural conformance; project managers govern project execution.
The 'Agile Exemption' Fallacy : Assuming that agile development squads are exempt from architecture governance because they are "autonomous." While agile teams have design freedom within their sprint backlogs, they must strictly adhere to enterprise architectural guardrails, data models, and interface contracts.
Rogue Technical Workarounds : Assuming that a project team can bypass enterprise security standards or introduce unapproved database engines if it helps them hit an aggressive delivery milestone. All deviations must be channeled through formal Change Requests.
The 'Rubber-Stamp' Compliance Anti-Pattern : Delaying all architectural reviews until the night before production deployment. When compliance reviews occur only at go-live, discovering non-compliance forces an impossible choice between catastrophic project delay and releasing defective architecture into production.