Contents:

Story maps are a great tool for digging deep into user journeys by mapping out all the steps the user does in the product. This information and user stories could be too granular to stakeholders who want to have a quick (and high-level overview) of what will happen around the product in the next few months or quarters.

Besides, as a product owner, you often start with a large chunk of backlog items (eg.: add a blog to an e-commerce website) which can be detailed later (as part of an existing story map, or on a brand new story map). So creating a roadmap of these large items could be helpful to:

Moreover, it provides an informative view for tracking the development's progression later on.

💡 Tip - Learn more about How to pick the right roadmap template.

Based on the connection with your backlog we offer two roadmap types:
​

Create a high-level overview of your initiatives on a single roadmap and track progression effortlessly. This roadmap allows you to schedule and visualize business or feature releases on a kanban-style roadmap. Use this template if you use releases for larger product increments, even from multiple story maps.You can now link individual story cards from multiple story maps to a roadmap card.

Use this template when features or epics are structured on the story map backbone. You can create a roadmap item from a single column or top-level card.

​

​

💡 Tip - Learn more about Create a release roadmap from a story map.

💡 Tip - Learn more about Create an epic roadmap from a story map.

Roadmaps are stored on the selected product entity. Select the right product then visit the "Roadmaps" menu.

Learn more about: