All Collections
Roadmap templates
How to pick the right roadmap template
How to pick the right roadmap template

Quick guide to choose a template the fits your workflow

Gergő Mátyás avatar
Written by Gergő Mátyás
Updated over a week ago


StoriesOnBoard offers multiple roadmap templates that fit the most product development use cases. To make the template selection easier we provided an intuitive wizard for you.

You can go through all the templates before selecting one of them to get a quick overview and a short introduction.

In order to select the right roadmap template you should answer the following questions:

Q1: How features or epics are grouped on your story map?

If you use the releases for larger grouping stories into functionalities then Release roadmaps or Portfolio roadmaps are great for you. If you start by linking a single story map you can add more sources by upgrading the release roadmap into a portfolio roadmap.

If you use the story map releases to slice the backlog into iterations (e.g. sprint 12, sprint 13), then you get more value from the Epic roadmap or High-level roadmap, where you can link multiple user stories as an epic to the roadmap card. Similar to release-based roadmaps, you can extend the number of story maps.

Q2: Are you working in quarterly time-boxes or just picking backlog items from the top of the backlog?

There are multiple ways to set up the column structure on the roadmap. Here are the most popular structures:

  • time-based: if you're working with deadlines or quarterly goals, choosing the Q1-Q2-Q3-Q4 structure will be easy-to-understand to every stakeholder. It's helpful in building a shared understanding among internal teams. Eg: the marketing team can plan the upcoming months or quarters.

  • priority-based: if your team is just delivering what's on the top of the priority list, you can organize items into the NOW-NEXT-LATER groups, so you can communicate what's on the dev team's table and what will come next. Plus, the 'Later' column shows the low-priority items

  • process-based: this template is useful to communicate the progress to the online teams or to the executives. So they can monitor what's happening in the dev team, what will come next, and what is already delivered.

Q3: Should you share everything from your story map?

Sometimes you have too many items on the story map and would narrow the scope. If you want to share just a hand-picked selection of backlog items, then skip the quick-add pop-up and add items manually.

All items are important? Don't worry, we save you a lot of time. Quick add feature links and organizes all items on your roadmap.

Learn more about roadmap templates

Did this answer your question?