EA Ready.
All study notes
Architecture Development Method8 minFree theory

Phase F in depth: from initial plan to approved projects

In this note

Key takeaways

  • Phase F turns work packages into approved projects with dates and resources.
  • It finalizes the roadmap and plan that Phase E drafted.
  • The plan must fit the change portfolio and existing management frameworks.
  • Decision-makers must understand the value and cost of each work package and transition.
  • The Implementation Governance Model prepares Phase G.
01

Purpose and essential knowledge

The practitioners’ guide gives Phase F a concrete result: an approved set of projects, each with its objective, any constraints, the resources required, and start and finish dates. Where Phase E reasoned in work packages, Phase F reasons in fundable projects.

The standard presents it as the way to move from Baseline to Target by finalizing a detailed Implementation and Migration Plan.

  • The resources available to undertake the change
  • How stakeholder priorities and preferences adjust to value, effort, and risk
02

Phase F objectives

The three objectives stress finalization, coordination with the rest of the enterprise, and decision-makers’ understanding of what is at stake.

  • Finalize the Architecture Roadmap and the Implementation and Migration Plan that supports it
  • Align that plan with how the enterprise manages and delivers change across its overall portfolio
  • Help key stakeholders understand the business value and cost of work packages and Transition Architectures
03

Key steps

FURTHER STUDY · APPLICATION DETAILS

Phase F steps move through framing, assessment, prioritization, and closing the cycle. The first is to confirm how the plan interacts with four management frameworks: business planning, Enterprise Architecture, portfolio and project management, and operations management.

  • Confirm interactions with the enterprise’s management frameworks
  • Assign a business value to each work package
  • Estimate resource needs, project durations, and delivery vehicles
  • Prioritize migration projects through cost/benefit analysis and risk validation
  • Confirm the roadmap, update the Architecture Definition Document, and complete the plan
  • Close the architecture development cycle and document lessons learned
04

Phase F outputs

Phase F delivers the finalized versions of the main architecture deliverables, prepares implementation governance, and may trigger further work. Lessons learned can also feed improvements to the architecture capability itself.

  • Detailed Implementation and Migration Plan and finalized Architecture Roadmap
  • Finalized Architecture Definition Document and Architecture Requirements Specification, Transition Architectures
  • Implementation Governance Model
  • Requests for Architecture Work for the architecture aspects of projects, Change Requests targeting the architecture capability

TERMS TO KNOW

The terms, in context.

Implementation and Migration Plan
A plan that orders, schedules, and resources the projects leading from Baseline to Target; initial in E, detailed in F.
Implementation Governance Model
A description of the processes, structures, roles, and measures that will frame project delivery.
Business Value Assessment
A technique that positions each work package by business value and risk to help prioritize.
Management frameworks
Business planning, Enterprise Architecture, portfolio and project, operations: the four arrangements the plan must fit with.