Introduction
TOGAF’s Architecture Development Method (ADM) is a comprehensive framework for enterprise architecture. Within this framework, Phase F: Migration Planning plays a pivotal role in ensuring a smooth transition from the current architectural state to the desired state. This phase focuses on the creation of a robust Implementation and Migration Plan, aligning with portfolio and project managers while considering dependencies, costs, and benefits of the transition architecture and migration projects.
The Migration Planning phase within TOGAF’s Architecture Development Method (ADM) is crucial for creating a comprehensive Implementation and Migration Plan. This plan aligns with the enterprise management frameworks and ensures that the transition architecture and migration projects are well-coordinated, considering dependencies, costs, and benefits. By coordinating with various enterprise management frameworks, this phase aims to deliver business value and ensure optimal resource utilization.
Objectives
The primary objectives of the Migration Planning phase are:
- Create a Viable Plan: Develop an Implementation and Migration Plan with portfolio and project managers.
- Assess Dependencies, Costs, and Benefits: Evaluate dependencies, costs, and benefits associated with the transition architecture and migration projects.
- Coordinate with Enterprise Management Frameworks: Align activities with Business Planning, Enterprise Architecture, Portfolio/Project Management, and Operations Management.
- Ensure Awareness and Adoption: Ensure that all organizational agencies are aware of the plan and adopt it accordingly with their ongoing activities.
- Establish Architecture Evolution Cycle: Set up an architecture evolution cycle to keep the architecture relevant amidst business and technological advancements.
Inputs
The Migration Planning phase takes into consideration the following inputs:
- Architecture Reference Materials
- Requests for Architecture Work
- Capability Assessment
- Communications Plan
- Organizational Model for Enterprise Architecture
- Governance Models and Frameworks
- Tailored Architecture Framework
- Statement of Architecture Work
- Architecture Vision
- Architecture Repository
- Draft Architecture Definition Document
- Draft Architecture Requirements Specification
- Change Requests
- Consolidated Architecture Roadmap
- Transition Architectures
- Implementation and Migration Plan
Steps
Step 1: Confirming Management Framework Interactions
- Work through the Implementation and Migration Plan to coordinate with other frameworks.
- Align activities with Business Planning, Enterprise Architecture, Portfolio/Project Management, and Operations Management.
Step 2: Assigning Business Value to Each Project
- Define and understand business value parameters.
- Consider Performance Evaluation Criteria, Return on Investment Criteria, Business Value, Critical Success Factors, Measures of Effectiveness, and Strategic Fit.
Step 3: Estimating Requirements, Timings, and Vehicles
- Determine resource requirements and timelines for each project.
- Provide initial cost estimates.
- Ensure availability and delivery of resources for each project.
Step 4: Prioritizing Migration Projects
- Use cost/benefit analysis and risk validation.
- Identify benefits of each project and determine appropriate priorities.
Step 5: Confirming Transition Architecture Increments
- Update the Architecture Definition Document with information about transition architecture(s).
Step 6: Generating the Architecture Implementation Roadmap
- Establish sequencing of the Implementation and Migration Plan.
- Ensure consistent addition of business value through timely execution of transition architecture projects.
Step 7: Establishing the Architecture Evolution Cycle
- Manage Enterprise Architectures and Transition Architectures as configuration items.
- Evolve throughout the lifecycle of varied solutions.
Outputs
The expected outputs of the Migration Planning phase include:
- Implementation and Migration Plan
- Finalized Architecture Definition Document
- Finalized Architecture Requirements Specification
- Finalized Architecture Roadmap
- Finalized Transition Architecture
- Re-usable Architecture Building Blocks
- Requests for Architecture Work
- Architecture Contracts
- Implementation Governance Model
- Change Requests
Phase Summary – Migration Planning (Phase F)
Here’s a summary of the TOGAF ADM Phase F: Migration Planning in a tabular format:
Aspect | Details |
---|---|
Objective | Create a viable Implementation and Migration Plan, aligning with enterprise frameworks. |
Inputs | – Architecture Reference Materials
– Requests for Architecture Work – Capability Assessment – Communications Plan – Organizational Model for EA – Governance Models and Frameworks – Tailored Architecture Framework – Statement of Architecture Work – Architecture Vision – Architecture Repository – Draft Architecture Definition Document – Draft Architecture Requirements Specification – Change Requests – Consolidated Architecture Roadmap – Transition Architectures – Implementation and Migration Plan |
Steps | 1. Confirm Management Framework Interactions
2. Assign Business Value to Each Project 3. Estimate Requirements, Timings, and Vehicles 4. Prioritize Migration Projects 5. Confirm Transition Architecture Increments 6. Generate Architecture Implementation Roadmap 7. Establish Architecture Evolution Cycle |
Outputs | – Implementation and Migration Plan
– Finalized Architecture Definition Document – Finalized Architecture Requirements Specification – Finalized Architecture Roadmap – Finalized Transition Architecture – Re-usable Architecture Building Blocks – Requests for Architecture Work – Architecture Contracts – Implementation Governance Model – Change Requests |
Result | Ensures a systematic approach to transition, considering business values, dependencies, and resources. Outputs serve as valuable artifacts for subsequent TOGAF ADM phases. |
Conclusion
In the Migration Planning phase, a structured approach is taken to craft a viable Implementation and Migration Plan. The inputs include essential architecture materials, requests for work, and various frameworks’ outputs. The steps involve confirming management framework interactions, assigning business value to each project, estimating requirements and prioritizing migration projects.
The phase ensures the relevance of architecture through the establishment of an architecture evolution cycle. The outputs include a comprehensive Implementation and Migration Plan, finalized architecture documents, roadmaps, and governance models. Together, these outputs set the stage for subsequent phases, providing a strategic guide for the enterprise’s architectural evolution.