Study guide

9.3 Implementation and Migration Plan Deliverable, Resource Allocation, and Transition Roadmaps

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

9.3 Implementation and Migration Plan Deliverable, Resource Allocation, and Transition Roadmaps

Key Takeaways Explain This Topic AI

The Implementation and Migration Plan is the Phase F deliverable that turns work packages into a schedule of projects, resources, and governance arrangements.

The Architecture Definition Document says what will be built, the Architecture Roadmap says in what sequence, and the Implementation and Migration Plan says how, by whom, and at what cost.

Transition Architectures are stable intermediate states that each deliver measurable business value, so a long transformation can pause safely between them.

TOGAF's final Phase F step is to complete the architecture development cycle and document lessons learned; an Implementation Governance Model can also be output.

Once the plan is agreed at the end of Phase F, an Architecture Contract may be drawn up with business stakeholders; contracts with implementing organizations are documented and signed at the beginning of Phase G.

Last updated: October 2026

9.3 Implementation and Migration Plan Deliverable, Resource Allocation, and Transition Roadmaps

The ultimate measure of an enterprise architecture practice is its ability to translate strategic vision into executed reality. Phase F culminates in the creation and formal approval of the Implementation and Migration Plan —the authoritative bridge connecting enterprise architecture to project execution. By finalizing the Architecture Roadmap and refining the Architecture Definition Document (ADD) to detail intermediate Transition Architectures , Phase F ensures that every participant, from executive sponsors to engineering project leads, understands what will be built, when it will be delivered, how resources are allocated, and how architectural governance will be enforced during implementation.

The Core Deliverable: Implementation and Migration Plan

According to the TOGAF Standard, 10th Edition, the Implementation and Migration Plan is the approved Phase F deliverable that provides the schedule, resource allocations, governance framework, and project portfolio required to implement the target architecture. While earlier phases produce architectural models, the Implementation and Migration Plan is a management deliverable co-developed with portfolio managers, the PMO, and corporate finance.

Detailed Anatomy of the Implementation and Migration Plan

A robust, exam-ready Implementation and Migration Plan contains six essential components:

Implementation and Migration Strategy : The overarching strategic approach guiding execution. It establishes whether the enterprise will adopt an incremental Strangler Fig pattern, a greenfield replacement, a commercial off-the-shelf (COTS) package rollout, or a phased regional deployment.

Project Charters and Work Package Definitions : Detailed operational charters for each implementation project derived from the architectural work packages. Each charter specifies project scope, business objectives, architectural building blocks (ABBs and SBBs) to be implemented, deliverables, acceptance criteria, and project boundaries.

Consolidated Implementation Schedule & Milestones : A time-sequenced project schedule establishing dependencies across work packages, critical path milestones, transition architecture cutover dates, and delivery checkpoints.

Resource Allocation and Financial Budgets : Comprehensive capital expenditure (CapEx) and operational expenditure (OpEx) commitments, internal staffing models, external systems integrator assignments, specialized hardware/software tooling allocations, and facilities requirements.

Governance and Compliance Framework : Specific governance mechanisms, including mandatory Architecture Board review gates, compliance criteria, stage-gate sign-offs, and procedures for requesting architectural dispensations during Phase G.

Risk Management and Contingency Protocols : Documented project and operational risks, fallback protocols, disaster recovery procedures, and rollback criteria in the event a production cutover encounters critical defects.

The Phase F Deliverables Triad

A critical area of testing on the OGEA-103 examination is distinguishing between the three core deliverables updated or finalized in Phase F: [ PHASE F DELIVERABLE TRIAD ]

  • |
  • +------------------------------------+------------------------------------+
  • | | |
  • v v v
  • [ Architecture Definition Document ] [ Architecture Roadmap ] [ Implementation & Migration Plan ]
  • The 'WHAT' (Models & Specifications) - The 'WHEN & IN WHAT SEQUENCE' - The 'HOW, WHO & AT WHAT COST'
  • Baseline Architecture Description - Chronological timeline - Executable project charters
  • Target Architecture Description - Transition Architectures - Resource assignments & budgets
  • Formal Transition Architectures (1-N) - Milestone dependencies - Work breakdown structures & PMO gates

Deliverable Dimension Architecture Definition Document (ADD) Architecture Roadmap Implementation and Migration Plan

Core Purpose Specifies what is being built across all architecture domains (baseline, transition, and target). Specifies when and in what sequence architectural increments and transition states occur over time. Specifies how , by whom , and at what financial cost the projects will be physically executed.

Primary Audience Enterprise architects, solution designers, domain specialists, technical leads. Business sponsors, portfolio managers, C-level executives, steering committees. Project managers, PMO, resource managers, procurement, financial controllers.

Key Contents Baseline/Target models, ABBs/SBBs, gap matrices, interface contracts, transition state models. Gantt-level transition milestones, capability increments, dependency arrows, work package timelines. Project charters, WBS, CapEx/OpEx cash flow profiles, staffing allocations, Phase G review gates.

Governance Role Establishes the technical baseline against which architectural compliance is evaluated. Communicates the strategic transformation path and capability realization trajectory. Serves as the operational contract authorizing project mobilization and expenditure of funds.

Transition Architectures: De-Risking the Journey

In complex enterprise environments, the distance between the baseline architecture and the target architecture is vast. Attempting to leap directly to the target state in a single, massive cutover—the infamous 'Big Bang' anti-pattern —almost universally leads to budget overruns, operational outages, and project cancellations. The TOGAF Standard solves this through Transition Architectures .

A Transition Architecture represents a formally defined, stable intermediate architectural state that delivers continuous business value and independent operational viability while progressively advancing toward the target architecture.

Principles of Transition Architectures

Independent Operational Viability : A transition architecture must never leave the enterprise in a half-finished, non-functional limbo. If executive leadership freezes funding at Transition Architecture 2 due to an economic downturn, the organization must be able to operate indefinitely and profitably in that state.

Measurable Business Value : Each transition state must deliver tangible business benefits (e.g., retiring an expensive mainframe subsystem, launching a mobile onboarding feature, or automating regulatory reporting) rather than purely invisible technical refactoring.

De-Risked Sequencing : High-risk dependencies are isolated and systematically neutralized across transition states using proven architectural patterns (e.g., deploying API mediation layers in Transition Architecture 1 before replacing back-end databases in Transition Architecture 2). [ Baseline Architecture ]

  • |
  • v (Work Packages: API Gateway, Cloud Infrastructure, Security)
  • [ Transition Architecture 1 ] ---> Delivers: Mobile Channel Access & \$1.2M Cost Savings
  • |
  • v (Work Packages: Microservices Ledger, Core Data Migration)
  • [ Transition Architecture 2 ] ---> Delivers: Real-time Payments & Decommission Legacy Core
  • |
  • v (Work Packages: AI Predictive Analytics, Global Expansion)
  • [ Target Architecture ] ---> Delivers: Full Autonomous Digital Enterprise
  • Resource Allocation and Capacity Planning

During Phase F, the enterprise architect collaborates with portfolio managers to align architectural demand with the organization's finite delivery capacity. This requires three distinct disciplines:

Resource Leveling : Adjusting project start dates and milestones to resolve resource over-allocation without extending overall roadmap delivery beyond executive deadlines. For example, if both the 'Customer Portal' and 'Claims Processing' work packages require the same dedicated identity security team, their identity integration sprints must be staggered sequentially.

Human Capital & Capability Uplift : Assessing whether internal engineering teams possess the necessary skills to support each transition state. The Implementation and Migration Plan must budget for training programs, external contractor augmentation, and knowledge transfer checkpoints.

Technical Environment Capacity : Managing the availability of non-production environments (development, integration testing, user acceptance testing, staging). Migration projects frequently fail because multiple project teams contend for a single shared legacy testing environment that cannot be replicated easily.

Securing Sponsor Sign-off and Architecture Board Approval

Before the plan is executed, the Implementation and Migration Plan is approved through the enterprise's governance and change-portfolio processes. TOGAF's own final Phase F step is to complete the architecture development cycle and document lessons learned. Approval typically involves:

Executive Business Sponsors : Sign off on the business cases, financial commitments (CapEx/OpEx), operational disruption windows, and capability release timelines.

Architecture Board : Formally reviews the updated Architecture Definition Document and Architecture Roadmap, verifying that all cross-domain dependencies are resolved, that transition states maintain architectural integrity, and that no unapproved deviations from enterprise architecture principles have been introduced.

Enterprise PMO & Portfolio Steering Committee : Confirms that project schedules, resource allocations, and vendor contracts are realistic and align with overall corporate delivery bandwidth.

Operations and Support Executives : Accept the operational readiness criteria, support handoff procedures, and legacy decommissioning schedules.

Securing this formal consensus prevents future disputes during implementation, ensuring that executive leadership remains unified when unexpected delivery challenges arise.

Transitioning to Phase G (Implementation Governance)

Phase F prepares the ground for Phase G (Implementation Governance) in three ways:

Implementation Governance Model : Phase F can output an Implementation Governance Model describing how implementation will be governed, including review points, roles, and how deviations are handled.

Compliance review schedule : Architecture Compliance reviews are typically planned for project initiation, initial design, major design changes, and ad hoc needs (Section 10.3), and are embedded in the project plans.

Dispensation route : The plan makes clear how implementation teams request time-bound dispensations from the Architecture Board when constraints force a temporary deviation.

TOGAF describes Architecture Contracts at several points in the ADM. The Statement of Architecture Work in Phase A is effectively one. When the Implementation and Migration Plan has been agreed at the end of Phase F , a contract may be drawn up between the architecting function and the business stakeholders who will build and deploy the architected solutions. At the beginning of Phase G , the contract with the function implementing the architecture, whether an in-house development team or a major contractor, is documented and signed by all developing organizations and the sponsoring organization. This happens in the Phase G step Guide development of solutions deployment .

Common Exam Traps & Practitioner Pitfalls

Confusing the Architecture Roadmap with the Implementation and Migration Plan : The Architecture Roadmap is an architectural view specifying the timeline of transition and target architectural states. The Implementation and Migration Plan is an executable management plan detailing project charters, resource allocations, funding approvals, and work breakdown structures.

The 'Big Bang' Cutover Fallacy : Recommending a single, direct transition from baseline to target architecture for complex systems, ignoring the necessity of defining stable, value-delivering Transition Architectures.

Skipping Formal Architecture Board Sign-off : Mobilizing development teams directly into implementation without securing formal Architecture Board approval and signed Architecture Contracts. On the exam, skipping governance gates is an automatic distracter.

Treating Transition Architectures as Throwaway Milestones : Failing to recognize that Transition Architectures must be independently viable operating states capable of sustaining business operations if subsequent phases are delayed or cancelled.

Loading diagram... Phase F Deliverables and the Hand-Off to Phase G