Key takeaways
- E combines realization opportunities into an initial roadmap.
- A transition is an architectural state rather than merely a date.
- Work packages connect objectives with actions.
From gaps to implementation work
Phase E, Opportunities and Solutions, explores how to realize the Target Architecture. It consolidates gaps identified across domains, considers solutions and dependencies, and groups change into work packages. It creates an initial coherent Architecture Roadmap, paying attention to business value and implementation conditions.
ABBs and repository assets help identify suitable SBBs. A gaps, solutions, and dependencies matrix can reveal work shared across several domains. Implementation factors include requirements, risks, assumptions, and constraints that need to remain visible in decisions.
Use intermediate states
A Transition Architecture describes a significant intermediate state between baseline and target. It is useful when change cannot be completed in one step, for example to maintain service continuity. It is not a landscape level like Strategic or Segment Architecture. A work package groups actions intended to achieve objectives; it may contribute to a project or program.
- Define stages that deliver observable value.
- Coordinate dependencies and shared elements.
- Prepare for Phase F to refine migration, priorities, and scheduling.
TERMS TO KNOW
The terms, in context.
- Transition Architecture
- Description of an intermediate state on the path towards the target.
- Work package
- Set of actions organized to achieve objectives.