Product Roadmap

Where is the product going to? When will this feature be available? 

The product roadmap is usually represented by a table to present the release schedule for a product showing the date when specific features will be available.

A product roadmap contains:

• vision and direction
• priorities in time: what will be done, later and in the future
• milestones to show the progress
• how they work be executed

Why do we need a roadmap?

A product roadmap serves many purposes:

1. it informs stakeholders about future versions
2. it establishes a common ground to define priorities
3. it provides transparence into the development of a product
4. it helps manage customer and management expectations

The existence of a roadmap allows the project owner to keep the product backlog trimmed and fit, with only the stories that will be addressed in the next 2 or 3 sprints.

Project managers can use a roadmap to manage users expectations by showing when they will have the features they want. The sooner people are informed of the release plan, the easier it is to convince them using rational arguments. Later in the process people may get frustrated and so emotional that any dialog may become really difficult. Some managers even talk about the importance of keeping credibility to maintain trust.