One of the deliverables that TOGAF® suggests and which I found very useful in my projects is the Road Map.

In TOGAF® standard is said: “This deliverable is incrementally developed throughout Phases E and F, and informed by readily identifiable roadmap components from Phase B, C, and D within the ADM®”

Why do I find it useful?

Because, already in early stages of project implementation, when there aren’t available many details, it can transfer import information, captures relevant elements by stakeholders feedback, gives a comprehensive timeframe of change initiative, steer the implementation of the project. Moreover, because it doesn’t use specialized notation, it can easily speak to different project stakeholder with different professional background, business and technical people, so this gives the possibility to collect different perspective contributions and engaging the stakeholder since the begin and through all the project over time.

Contents of a project Roadmap can be different, TOGAF® suggests these:

■ Work package portfolio:

— Work package description (name, description, objectives, deliverables)

— Functional requirements

— Dependencies

— Relationship to opportunity

— Relationship to Architecture Definition Document and Architecture Requirements

Specification

— Business value

■ Implementation Factor catalog, including:

— Risks

— Issues

— Assumptions

— Dependencies

— Actions

— Inputs

■ Consolidated Gaps, Solutions, and Dependencies matrix, including:

— Architecture domain

— Gap

— Potential solutions

— Dependencies

■ Any Transition Architectures

■ Implementation recommendations:

— Criteria measures of effectiveness of projects

— Risks and issues

— Solution Building Blocks

The work packages involved, their responsibility, their relationship and how they arranged over time is typically graphically depicted by a diagram. The Roadmap View is a specific type of view that is proposed in the ArchiMate® model to this purpose.

Below I give an example of road map view for a project that aims to migrate to a new version of a department system.

This is what I know …so far.