6.2 Phase F: Migration Planning
Key Takeaways
- Phase F finalizes the Architecture Roadmap and the supporting Implementation and Migration Plan.
- Phase F ensures the Implementation and Migration Plan is coordinated with the enterprise's approach to managing change across its overall change portfolio.
- Phase F ensures key stakeholders understand the business value and cost of work packages and Transition Architectures.
- Phase F prioritizes migration projects through a cost/benefit assessment and risk validation after assigning business value to each work package.
- Phase F outputs include the detailed Implementation and Migration Plan, finalized Architecture Roadmap, and the Implementation Governance Model.
6.2 Phase F: Migration Planning
Phase F addresses how to move from the Baseline to the Target Architectures by finalizing a detailed Implementation and Migration Plan. The Foundation syllabus asks you to briefly explain the purpose of Phase F and describe its objectives.
Objectives of Phase F
- Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan
- Ensure that the Implementation and Migration Plan is coordinated with the enterprise's approach to managing and implementing change in the enterprise's overall change portfolio
- Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders
Where Phase E worked out what could be delivered and in what increments, Phase F turns that into an agreed, prioritized plan that fits the organization's portfolio, project, and operations management processes.
Steps of Phase F
- Confirm Management Framework Interactions for the Implementation and Migration Plan — coordinate with business planning, Enterprise Architecture, portfolio and project management, and operations management
- Assign a Business Value to Each Work Package — using criteria such as performance evaluation criteria, return-on-investment criteria, business value, critical success factors, measures of effectiveness, and strategic fit, and considering risks
- Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle
- Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation
- Confirm Architecture Roadmap and Update Architecture Definition Document
- Complete the Implementation and Migration Plan
- Complete the Architecture Development Cycle and Document Lessons Learned
Collaboration with Portfolio and Project Management
The Partnership Dynamic
Phase F is a co-design exercise bridging enterprise architecture and project portfolio management:
- The Enterprise Architect's Perspective: Focuses on strategic alignment, architectural coherence, minimizing technical debt, preserving data integrity, and respecting structural cross-domain dependencies (e.g., ensuring a core platform API layer is deployed before client channels are migrated).
- The Portfolio and Program Manager's Perspective: Focuses on capital expenditure ceilings, operational staffing constraints, procurement contracting timelines, vendor delivery capacities, and balancing transformation initiatives against business-as-usual operations.
- The Collaboration Process: Architects provide work packages, dependency maps, and technical risk assessments; portfolio planners overlay financial schedules, resource allocations, and portfolio governance frameworks (such as PMBOK, PRINCE2, or enterprise Agile portfolio management). Together, they produce a realistic, executable Implementation and Migration Plan.
Business Value, Cost, and Risk
TOGAF's Business Value Assessment Technique helps stakeholders compare work packages by plotting them on a matrix of value against risk. Work packages with high value and low risk are strong early candidates; high-risk, low-value work packages are questioned or deferred. This technique supports Phase F objective 3 — making sure stakeholders understand the business value and cost of each work package and Transition Architecture.
Other migration planning techniques used in Phases E and F include the Architecture Definition Increments Table, which lists the projects and their incremental deliverables across Transition Architectures, and the Transition Architecture State Evolution Table, which shows the proposed state of architecture building blocks at each transition.
Prioritization Matrix & Worked Transformation Scenario
To establish an objective implementation sequence, architects and portfolio managers map candidate work packages onto a Prioritization Matrix balancing business value against implementation complexity and risk:
| Work Package Code & Title | Strategic Business Value | Technical & Operational Risk | Readiness & Dependency Factors | Prioritization Category & Recommended Sequence |
|---|---|---|---|---|
| WP-01: Cloud Identity & Access Federation | High (enables secure access across all initiatives) | Low (mature enterprise COTS pattern) | High readiness; zero internal technical prerequisites | Quick Win / Foundation (Sequence 1): Deploy immediately to establish identity fabric for all downstream projects. |
| WP-02: Real-time Event Streaming Bus | Moderate (foundational infrastructure) | Moderate (new architecture paradigm) | Moderate readiness; depends on network infrastructure | Foundational Enabler (Sequence 2): Deploy early to unlock data integration across application domains. |
| WP-03: AI Predictive Customer Churn Engine | High (direct marketing revenue upside) | High (complex ML pipeline & model governance) | Low readiness; strictly dependent on WP-01 and WP-02 for customer event feeds | Strategic Transformation (Sequence 3): Schedule for later transition once foundational data pipelines are proven. |
| WP-04: Legacy Batch Billing Rewriting | Low (internal operational optimization) | High (fragile legacy code & high regression risk) | Low readiness; high operational risk | Defer or De-prioritize (Sequence 4): Encapsulate with APIs rather than rewriting; re-evaluate in future ADM cycles. |
Finalizing Transition Architectures and Deliverables
Phase E provides an incomplete Architecture Roadmap and Implementation and Migration Plan; Phase F integrates them with the enterprise's other change activity. Transition Architectures identified in Phase E are confirmed through the Phase F steps:
- Business value and cost: each work package is assigned a business value, and migration projects are prioritized through a cost/benefit assessment and risk validation, so stakeholders understand what each Transition Architecture delivers.
- Resources and delivery vehicles: resource requirements, project timings, and availability or delivery vehicles are estimated for the work in each transition.
- Finalized deliverables: the step "Confirm Architecture Roadmap and Update Architecture Definition Document" leads to a finalized Architecture Definition Document (ADD), including finalized Transition Architectures if any, and a finalized Architecture Requirements Specification (ARS).
Deliverable Distinction: Architecture Roadmap vs. Implementation and Migration Plan
It is important to distinguish the Architecture Roadmap from the Implementation and Migration Plan:
| Dimension | Architecture Roadmap | Implementation and Migration Plan |
|---|---|---|
| Typical Lead | Enterprise Architecture team | Developed jointly with portfolio, program, and project management |
| Primary Focus | The evolution of architectural states over time (Baseline → Transition 1 → Transition 2 → Target Architecture) | The physical execution of projects, resources, capital allocation, and management controls |
| Primary Audience | Architecture Board, CIO/CTO, Business Strategists, Domain Architects | Project Managers, PMO, Finance, Steering Committees, Delivery Teams |
| Core Content | Architecture Building Blocks, Transition Architectures, gap closure mappings, technology obsolescence timelines | Work Breakdown Structures (WBS), project charters, Gantt charts, budgets, resource leveling, risk registers |
| ADM Lifecycle Role | Initial complete version created in Phase E; finalized in Phase F; guides Phase G | Draft with strategy in Phase E; completed in Phase F; used to govern execution in Phase G |
Outputs of Phase F
| Output | Notes |
|---|---|
| Implementation and Migration Plan (detailed) | Includes the implementation and migration strategy, interactions with other management frameworks, and the project and portfolio breakdown of the implementation |
| Finalized Architecture Definition Document | Updated to reflect the confirmed roadmap |
| Finalized Architecture Requirements Specification | Updated where needed |
| Finalized Architecture Roadmap | Confirmed work package sequence and Transition Architectures |
| Transition Architecture | Updated where applicable |
| Re-usable Architecture Building Blocks | Made available in the repository |
| Request for Architecture Work | For a new iteration of the ADM cycle, if needed |
| Implementation Governance Model | Defines how implementation of the Transition Architecture will be governed; used in Phase G |
| Change Requests | For the Architecture Capability, arising from lessons learned |
Common Exam Pitfalls
- Attributing plan finalization to Phase E. Phase E creates the initial complete roadmap and draft plan; Phase F finalizes them.
- Planning in isolation. Phase F must coordinate the plan with the enterprise's overall change portfolio and management frameworks.
- Forgetting the Implementation Governance Model. It is a Phase F output consumed in Phase G.
- Overlooking lessons learned. Phase F completes the architecture development cycle and documents lessons learned.
Which statement is an objective of Phase F: Migration Planning?
How are migration projects prioritized in Phase F?
Which Phase F output defines how implementation will be governed and is consumed in Phase G?
Which statement correctly distinguishes Phase E from Phase F?