Skip to content

7. Techniques

7.10 Product Roadmap

Agile Extension to the BABOK® Guide

Product Roadmap is used to communicate direction and progress towards the vision for a solution or initiative, and it measures progress against that vision through achieving the stakeholders' desired outcome.

Product Roadmap is a strategic document and plan used to describe how a product is likely to grow, to align to stakeholders' needs, and to acquire a budget for delivery. It shows features, requirements, or initiatives, and outlines a path to deliver them over time.

Agile values working solutions; product roadmaps focus on product/feature/ value delivered, not milestones or check points.

Product Roadmap enables iterative delivery by expressing features in terms of now, next, and later. It defines what the solution is and what it is not.

Figure 7.10.1: Product Roadmap



.1 Defined Vision and Strategy

Product Roadmap clearly defines the vision and strategy for the initiative. This vision clarifies what is included for the solution and the goal to be achieved. The roadmap also articulates how that vision will be achieved.

.2 Defined Desired Outcomes

Product Roadmap clearly articulates organization and stakeholder desired outcomes. Defining the desired outcomes helps the delivery team provide a working solution that adds value.

.3 Product Management Team

The product management team is led by the product owner or customer representative. This is a small team focused on maintaining the Product Roadmap. The product management team ensures the roadmap reflects the most current priorities and goals, is accessible to those who need it, and tailors the view based on the audience as needed.

.4 Themes

Product Roadmap includes themes which represent a collection of requirements, features, or stories.

.5 High-level Requirements

Product Roadmap is comprised of high-level requirements or features which are expected to deliver value to achieve the vision and goals for the solution. These high-level items represent a group of requirements or stories.

.1 Strengths
  • It is visible and accessible to all stakeholders.

  • It orients stakeholders to a shared focus.

  • It presents a unified view of the solution direction.

  • It can be used to facilitate a discussion of options and priorities.

  • There can be different views based on the audience for the information. For example, organization executives, solution team, and external customers may have different views of the roadmap.
.2 Limitations
  • Ineffective if the organizational environment leads to a frequently changing vision and desired outcomes.

  • Can be misused as a milestone or date-driven roadmap.

  • Time-consuming to maintain if overly detailed or multiple different views are required.