Key takeaways
- F refines and finalizes migration; G governs implementation.
- Scheduling must respect dependencies and available resources.
- Transformation includes organizational as well as technical work.
Balance value, cost, and sequencing
Phase F, Migration Planning, finalizes the Architecture Roadmap and Implementation and Migration Plan. It checks that costs, benefits, risks, and resources are understood sufficiently to prioritize work. Dependencies and constraints determine a realistic sequence; business priority alone is insufficient when an essential prerequisite is unavailable.
Planning should connect with portfolio, program, and project practices. Outputs may specify projects, work groupings, milestones, responsibilities, and initiation conditions. Architecture contributes coherence to change; project management retains responsibility for detailed execution.
Prepare implementation governance
The Implementation Governance Model defines how compliance and decisions will be monitored: roles, processes, checkpoints, and criteria. It establishes an understandable operating approach before teams implement solutions. Planning should also consider readiness and identified risks, including training and change-support actions.
- Check the value and cost of each stage.
- Coordinate teams around shared dependencies.
- Plan controls and responsibilities before implementation starts.
TERMS TO KNOW
The terms, in context.
- Implementation and Migration Plan
- Work plan for realizing and migrating towards intended architecture states.
- Implementation Governance Model
- Arrangement of implementation decisions and controls.