Roadmap
Short Tip: It is a high-level map about the main product releases.
What is it?
It is a high-level map used for communication with stakeholders in different areas of product building.
The Roadmap has the main activities to be developed in order to build the product, but it doesn’t usually include specific release dates in an agile approach (PIM-Go© Agile). On the other hand, with predictive projects (PIM-Go© Hybrid), dates can be added.
Why use it?
The Product Backlog and Story Map are highly granular artifacts, which makes them too detailed for communication with stakeholders, especially high-level ones (managers and C-Level).
Unlike a traditional Gantt timeline, the Roadmap emphasizes an overview of activities and releases, rather than precise details on when they will occur.
How to use it?
The Roadmap is usually implemented using digital tools, since stakeholders are not part of the team and are not physically present in the team’s physical environment.
It is built by the Product Owner (PIM-Go© Agile) or the Initiative Leader (PIM-Go© Hybrid) in coordination with the Program Leader.
A simple model is the Goal Oriented Roadmap (GO Roadmap) created by Roman Pichler. In order to use it you should:
- Define the frequency to be used in the Roadmap (monthly, quarterly, etc.);
- For each release, indicate:
- A significant name that translates the release’s concept;
- The goal that is being achieved;
- The high-level functionalities delivered;
- The metrics to be used in order to check whether the goal was achieved.
It is important to note that this Roadmap includes only releases related to the product built. Thus, other activities outside this scope, yet necessary for the release are not included (e.g., marketing and legal actions, mobilization of the sales team, etc.). Depending on the need to mobilize stakeholders in those areas, a more complete Roadmap can be used.