Architecture Roadmap (TOGAF)
A TOGAF deliverable showing the timeline for transitioning from the baseline architecture to the target architecture, including work packages, milestones, and the sequence of transition architectures.
Purpose
The TOGAF Architecture Roadmap provides a time-sequenced view of how the architecture will evolve, enabling programme planning, resource allocation, and investment decisions. It shows the path from current state to target state in manageable increments.
When to Use
Create during TOGAF Phase E (Opportunities and Solutions) and Phase F (Migration Planning). Update as implementation progresses and priorities shift.
How to Build
Start with the gap analysis between baseline and target architecture. Identify all the changes needed across business, data, application, and technology domains.
Group changes into work packages that can be delivered together. Consider dependencies, risk, and value delivery when grouping.
Sequence work packages on a timeline considering: dependencies between packages, resource availability, risk (do high-risk items early), and value delivery (deliver value incrementally).
Define transition architectures — stable intermediate states between baseline and target. Each transition should be operational and deliver value.
Include decision points where the roadmap may need to adapt based on outcomes from earlier phases.
Tips
- Align with financial planning cycles — work packages should map to budget periods.
- Show dependencies clearly — they drive the sequence more than anything else.
- Include both build and decommission activities.
- Mark decision points where the roadmap may pivot.
- Keep it at the right level of detail — too detailed and it becomes unmanageable.
Common Mistakes
- Creating a roadmap that is too detailed and becomes stale quickly.
- Not showing dependencies between work packages.
- Ignoring decommissioning of legacy systems.
- Not including decision points where the roadmap may need to adapt.
- Treating the roadmap as fixed rather than a living plan.
Government Context
In UK government, architecture roadmaps support Spending Review submissions and CDDO spend control processes. They should align with departmental transformation plans and cross-government platform adoption timelines. The roadmap should show how legacy IT risk is being addressed progressively. IPA gateway reviews will assess whether the roadmap is realistic and achievable.