Phase E · Opportunities & SolutionsTGF-PE · theory

Source · TOGAF Standard, 10th Edition — ADM: Phase E

Why this matters

ADM — Phase E

Phase E is the pivot from architecture to delivery. It's the first phase directly concerned with implementation: it takes the consolidated gaps from B/C/D and turns them into a plan of work packages and candidate delivery vehicles.

The concept

Phase E §Objectives

Phase E — Opportunities & Solutions — generates the initial, complete version of the Architecture Roadmap. It consolidates gaps across all domains, groups them into work packages, identifies Transition Architectures (intermediate states that deliver business value), and decides the overall implementation approach (make/buy/reuse).

Transition Architectures

Phase E §Steps

A Transition Architecture is a formally described intermediate architecture state between Baseline and Target that delivers value along the way. Phase E defines these so a large transformation can be delivered incrementally rather than big-bang. The output is a first-cut Implementation and Migration Plan and the Architecture Roadmap.

How it connects

ADM flow

Phase E consumes gaps from B/C/D, and its first-cut plan is detailed and costed in Phase F. Work packages become the basis for Architecture Contracts governed in Phase G.

Common traps
  • Phase E is the first implementation-oriented phase — it produces the first-cut plan, not the final one (that's F).
  • Transition Architectures are intermediate value-delivering states — a defining Phase E concept.
  • Phase E consolidates gaps from all domains and groups them into work packages.
Key takeaways
  • Phase E: consolidate gaps → work packages + Transition Architectures + Architecture Roadmap.
  • First phase concerned with implementation; produces the first-cut migration plan.
  • Detailed planning follows in Phase F.