5.3 Phase F: Migration Planning, Roadmap Development & Portfolio Prioritization
Key Takeaways
- Phase F prioritizes Work Packages and finalizes the authoritative Implementation and Migration Plan (IMP) in close alignment with Enterprise Portfolio Management.
- TOGAF names five Migration Planning Techniques: the Implementation Factor Assessment and Deduction Matrix; the Consolidated Gaps, Solutions, and Dependencies Matrix; the Architecture Definition Increments Table; the Transition Architecture State Evolution Table; and the Business Value Assessment Technique.
- The Architecture Definition Increments Table is organized by project and shows what each delivers per transition state, while the Transition Architecture State Evolution Table is organized by service and shows the state of each Solution Building Block.
- The Business Value Assessment Matrix evaluates Work Packages along dual axes of Business Value and Implementation Risk/Cost to determine project sequencing and funding allocation.
- Phase F finalizes the Architecture Roadmap and updates governance baselines including the Architecture Definition Document (ADD) and Architecture Requirements Specification.
5.3 Phase F: Migration Planning, Roadmap Development & Portfolio Prioritization
While Phase E identifies potential opportunities, groups domain gaps into candidate Work Packages, and outlines initial Transition Architectures, Phase F: Migration Planning takes those candidate initiatives and conducts rigorous prioritization, cost-benefit modeling, risk assessment, and portfolio scheduling.
The central objective of Phase F is to produce a fully finalized, resource-constrained, executive-approved Implementation and Migration Plan (IMP) and an updated Architecture Roadmap that integrates seamlessly with corporate IT Project Portfolio Management (PPM) and enterprise business budgeting frameworks.
Primary Objectives of Phase F
The core goals of ADM Phase F are:
- Finalize the Architecture Roadmap: Transition candidate roadmaps from Phase E into a fully sequenced, realistic schedule aligned with enterprise strategic priorities and operational delivery capacity.
- Finalize the Implementation and Migration Plan (IMP): Create the authoritative master plan detailing project charters, resource allocations, business value milestones, dependencies, and risk mitigation strategies.
- Prioritize Migration Projects: Evaluate Work Packages using formal decision matrices balancing business value against implementation risk, financial cost, and operational complexity.
- Align EA with Corporate Management Frameworks: Integrate architectural initiatives into corporate Project Portfolio Management (PPM), Enterprise Risk Management (ERM), operations management, and annual capital budgeting processes.
- Secure Executive Sponsor Sign-Off: Conduct final stakeholder reviews with the Architecture Review Board (ARB), Chief Information Officer (CIO), Chief Financial Officer (CFO), and business unit leaders to finalize funding approvals.
The Five TOGAF Migration Planning Techniques
TOGAF's ADM Techniques document collects five named Migration Planning Techniques used across Phases E and F. Foundation questions test them by name, so learn what each artifact produces, not just that it exists.
| # | Technique | What it produces | Where it is used |
|---|---|---|---|
| 1 | Implementation Factor Assessment and Deduction Matrix | A register of the factors that will affect the Implementation and Migration Plan, each with a description and the deduction drawn from it. | Phase E |
| 2 | Consolidated Gaps, Solutions, and Dependencies Matrix | The gaps from the Phase B, C, and D gap analyses gathered into one table, each grouped against potential solutions and dependencies, so they can be assembled into work packages. | Phase E |
| 3 | Architecture Definition Increments Table | A plan of a series of Transition Architectures, listing each project and the incremental deliverable it contributes at each transition state. | Phase E/F |
| 4 | Transition Architecture State Evolution Table | The proposed state of the architecture at each transition, mapping Solution Building Blocks against service categories and marking each service as new, retained, transitioned, or replaced. | Phase E/F |
| 5 | Business Value Assessment Technique | A value-versus-risk comparison of candidate projects, used to prioritize them — see the matrix below. | Phase F |
1. Implementation Factor Assessment and Deduction Matrix
The matrix has three columns — Factor, Description, and Deduction. Typical factors are risks, issues, assumptions, dependencies, actions, and impacts. The value is in the third column: a factor on its own is just an observation, while the deduction states what the architecture or the plan must therefore do about it.
| Factor | Description | Deduction |
|---|---|---|
| Procurement process rollout | Business units run their own purchasing processes on separate tooling. | Business-unit stakeholder sponsorship must be secured before the shared process ships, and an enterprise prioritization framework must exist first. |
| Data-center lease expiry | The primary facility contract ends in 18 months. | The technology transition must complete inside 18 months, which fixes the outer bound of the roadmap. |
2. Consolidated Gaps, Solutions, and Dependencies Matrix
Phases B, C, and D each produce their own gap analysis. This matrix rationalizes them into a single numbered list so that one solution can be recognized as answering several gaps at once, and so that dependencies between them become visible.
| No. | Architecture | Gap | Potential solutions | Dependencies |
|---|---|---|---|---|
| 1 | Business | New order-processing process | Adopt COTS process; build custom | Drives item 2 |
| 2 | Application | New order-processing application | COTS package; in-house build | Depends on item 1 |
| 3 | Data | Consolidated customer information base | COTS customer base; customer data mart | — |
The grouped rows are what become work packages, which is the direct handoff from Phase E into the prioritization work of Phase F.
3. Architecture Definition Increments Table
This table plans a series of Transition Architectures by showing what each project delivers at each transition state, so stakeholders can see capability accumulating rather than a single distant cutover.
| Project | Transition State 1 | Transition State 2 | Target State |
|---|---|---|---|
| Procurement process | Policy, data handling, and infrastructure updated | Procurement, IT, and business-unit staff trained | Whole enterprise on the new process |
4. Transition Architecture State Evolution Table
Where the increments table is organized by project, the state evolution table is organized by service: it lists the Solution Building Blocks against the service categories of the technology taxonomy and marks, for each transition state, whether a service is new, retained, transitioned, or replaced. (Historically this was demonstrated against the TRM's service categories; any taxonomy your enterprise has adopted serves the same purpose — see Section 10.2.)
Exam trap: items 3 and 4 are easy to swap. Increments table = by project, what each one delivers per transition. State evolution table = by service/SBB, what state each one is in per transition. Note also that the older TOGAF 9 text called item 4 the Enterprise Architecture State Evolution Table; the certification material uses Transition Architecture State Evolution Table.
The Business Value Assessment Matrix
A pivotal technique in Phase F prioritization is the Business Value Assessment Matrix. This tool evaluates each proposed Work Package across two primary analytical dimensions:
- Perceived Business Value: The strategic importance, financial ROI, revenue growth potential, customer experience enhancement, or regulatory compliance necessity of the initiative.
- Implementation Risk and Cost: The technical complexity, organizational change difficulty, financial investment, and potential operational disruption associated with executing the work package.
+-----------------------------------------------------------------------------+
| BUSINESS VALUE ASSESSMENT MATRIX |
+-----------------------------------------------------------------------------+
| HIGH VALUE / LOW RISK | HIGH VALUE / HIGH RISK |
| Priority 1: "Quick Wins" | Priority 2: Strategic Initiatives |
| - Execute immediately | - Requires careful phased delivery |
| - High ROI, fast payback | - Formulate Transition Architectures |
+-------------------------------------+---------------------------------------+
| LOW VALUE / LOW RISK | LOW VALUE / HIGH RISK |
| Priority 3: Tactical Improvements | Priority 4: Eliminate / Re-evaluate |
| - Execute when resources permit | - Reject candidate project |
| - Minor efficiency gains | - Unfavorable ROI vs. disruption risk |
+-----------------------------------------------------------------------------+
Using this evaluation framework:
- High Value / Low Risk (Quick Wins): Scheduled for immediate implementation in early transition phases to generate momentum and demonstrate EA business value.
- High Value / High Risk (Strategic Initiatives): Structured into detailed Transition Architectures (from Phase E) with explicit risk-mitigation checkpoints before capital release.
- Low Value / Low Risk (Tactical Improvements): Deferred to later implementation phases or executed opportunistically when excess capacity exists.
- Low Value / High Risk: Rejected or returned to business sponsors for re-scoping.
Key Deliverables of Phase F
Phase F produces and updates several critical governance deliverables:
1. Implementation and Migration Plan (IMP)
The IMP is the master governance document that directs project execution teams. It contains:
- Implementation Strategy: High-level approach (e.g., evolutionary migration, parallel operation, phased strangulation).
- Project Charters: Formally defining project scope, objectives, executive sponsors, lead architects, and budget allocations.
- Work Package Schedules: Time-sequenced project timelines with clear critical path identification.
- Resource Allocation Plan: Human, technical, and financial resource commitments.
- Governance Control Checkpoints: Gates requiring Architecture Review Board (ARB) compliance audits before proceeding across transition phases.
2. Finalized Architecture Roadmap
The Architecture Roadmap provides a visual, time-aligned representation of target business capabilities, application portfolio transitions, data migration milestones, and technology platform deployments across all Transition Architectures.
3. Architecture Definition Document (ADD) & Requirements Updates
During Phase F, the master ADD and Architecture Requirements Specification are updated to capture final implementation constraints, vendor procurement decisions, and negotiated scope adjustments.
ADM Execution Steps in Phase F
Phase F follows six detailed ADM execution steps:
- Confirm Management Framework Interactions: Align implementation planning with corporate PPM, IT service management (ITSM), and risk management governance.
- Assign Business Value to Each Work Package: Quantify financial ROI, cost reduction, risk reduction, and strategic enablement for each package.
- Estimate Resource Requirements, Timings, and Costs: Engage project management offices (PMO) and infrastructure teams to generate detailed cost and effort estimates.
- Prioritize Migration Projects: Apply the Business Value Assessment Matrix and dependency modeling to establish project sequencing.
- Finalize Architecture Roadmap and IMP: Synthesize all project charters, schedules, matrices, and resource plans into the master IMP.
- Complete Architecture Development: Conduct final architecture reviews, archive artifacts in the Architecture Repository, and hand off execution oversight to project delivery teams.
What is the primary governance deliverable produced and finalized in ADM Phase F?
How are Work Packages prioritized using the Business Value Assessment Matrix in Phase F?
In Phase F prioritization, how should an architectural initiative classified as 'High Business Value / High Risk' be managed?
An architect needs a single artifact showing, for each Solution Building Block, whether the service it delivers is new, retained, transitioned, or replaced at each transition state. Which Migration Planning Technique produces that view?