Product Roadmapping

Learn how to create a powerful agile product roadmap that helps you describe how your product is likely to grow and aligns the stakeholders.

A product roadmap is a powerful tool to describe how a product is likely to grow, to align the stakeholders, and to acquire a budget for developing the product. But creating an effective roadmap is not easy, particularly in an agile context where changes occur frequently and unexpectedly. In this episode, I share ten practical tips to helps you create an actionable agile product roadmap.

Seven proven techniques to help you answer it, and prioritize a product roadmap.

Try Needs, Wants and Wishes instead of MoSCoW when prioritizing.

There are several ways to prioritize a product backlog but Mike Cohen clearly disagrees with the MoSCoW (Must, Should, Could, Will not have) prioritization technique in this article citing that the method fails to consider items placed in the could-have category and is used to sort out product requirements for a non-agile project. Instead, through an approach that he borrows from his financial planner, he suggests projects to try needs, wants, and wishes. The agile coach notes that the new method has worked well with 3 companies he tried and he finds it a lot easier to explain wants vs. wishes than explaining could-haves.

Learn how to create a powerful agile product roadmap that helps you describe how your product is likely to grow and aligns the stakeholders.

A product roadmap is a powerful tool to describe how a product is likely to grow, to align the stakeholders, and to acquire a budget for developing the product. But creating an effective roadmap is not easy, particularly in an agile context where changes occur frequently and unexpectedly. This post shares ten practical tips to helps you create an actionable agile product roadmap.

An overview of the GO product roadmap: a goal-oriented, agile roadmap that effectively captures how your product is likely to evolve.

Find out how the product roadmap and the product backlog relate, and who should own the two artefacts.

This article explains how making you product roadmap goal-oriented (or outcome-based), shared, and actionable allows you to fully leverage it.