Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo
StoriesOnBoard
Must-have product management
tool with PRODUCT ROADMAP
www.storiesonboard.com
Product Roadmap
By
www.storiesonboard.co
End-to-end product management tool
Build lovable products together from idea to reality
Insight Management
Streamline feedback into
a single repository
User Story Map
Boost product discovery
and shared understanding
Product Roadmap
Connect to story maps
and releases
Prioritization
Data-driven decisions
always one step ahead
www.storiesonboard.com
Purpose of roadmap
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:
gain an oversight on
prioritize
schedule
large backlog items. Moreover, it provides an informative view for
tracking the development's progression later on.
Roadmap by
www.storiesonboard.com
Q1 Q2 Q3 Q4
TEAM
1
TEAM
2
Purpose of roadmap
As above described, roadmaps are helpful when you plan a new product
or new features for a running product. Steps could be the followings:
1 Create a roadmap and create a card for each product
component (or feature idea)
Have a prioritization session and decide what's going to
be developed first
Detail the top-priority items by mapping out the user
journey on a story map (or extend your product's story
map with the new epic)
Arrange/schedule the rest of the roadmap items
Invite stakeholders to the roadmap
Roadmaps are also useful when you have already done the story
mapping session and the releases are scheduled. In this case, the
roadmap provides a convenient board to track the development's
progression. The steps are the following:
Pick a roadmap template that suits your needs
Decide how to group the items into columns eg:
Q1
-
Q2
-
Q3 or NOW
-
NEXT
-
LATER
Link a story map (or multiple story maps) to the roadmap
Import story map items (Hint: use the quick-add option
when creating the roadmap)
Invite stakeholders to the roadmap
2
3
4
5
1
2
3
4
5
www.storiesonboard.com
You’ve got a question?
Let’s discuss how we can help you
Book a demo
How to pick the right roadmap template
www.storiesonboard.com
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.
Roadmap by
In order to select the right roadmap template you should answer
the following questions:
How features or epics are grouped on your story map?
Are you working in quarterly time-boxes or just picking
backlog items from the top of the backlog?
Should you share everything from your story map?
1
2
3
Build your own product roadmap
Try Roadmap
How to pick the right roadmap template
How features or epics are grouped on your story map?
1
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.
Are you working in quarterly time-boxes or just picking
backlog items from the top of the backlog?
2
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.
www.storiesonboard.com
There are multiple ways to set up the column structure on the
roadmap. Here are the most popular structures:
How to pick the right roadmap template
Should you share everything from your story map?
3
www.storiesonboard.com
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.
Product roadmap templates on StoriesOnBoard
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.
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, and everything is managed
within the same story map.
Release roadmap
Learn more
How to pick the right roadmap template
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.
If you grouped features into large business releases across multiple
story maps, this template is for you. Create a high-level overview of
your initiatives on a single roadmap and track progression effortlessly.
www.storiesonboard.com
Epic roadmap
Portfolio roadmap
Learn more
Learn more
How to pick the right roadmap template
High-level roadmaps allow you to visualize large-backlog items from
multiple story maps on an easy-to-understand board. You can group
roadmap items with swimlanes for a better visuality.
High-level roadmap
Create a custom roadmap with items created from scratch. This
roadmap type allows you to create visualize high-level or company
initiatives.
Single roadmap
www.storiesonboard.com
Product Roadmap
Connect to Story Maps & Releases
Start FREE Trial
Learn more
Learn more
www.storiesonboard.com
Product Management on StoriesOnBoard
StoriesOnBoard
is a lightweight product management tool built around user story
mapping. A visual, intuitive, and collaborative solution for product
managers to put customer value first.
You’ve got a question?
Let us know and let’s discuss
what are the best practices.
Start FREE Trial
End-to-end product management
Build lovable products together from idea to reality
www.storiesonboard.com

More Related Content

StoriesOnBoard Product Roadmap.pdf

  • 1. StoriesOnBoard Must-have product management tool with PRODUCT ROADMAP www.storiesonboard.com Product Roadmap By
  • 2. www.storiesonboard.co End-to-end product management tool Build lovable products together from idea to reality Insight Management Streamline feedback into a single repository User Story Map Boost product discovery and shared understanding Product Roadmap Connect to story maps and releases Prioritization Data-driven decisions always one step ahead www.storiesonboard.com
  • 3. Purpose of roadmap 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: gain an oversight on prioritize schedule large backlog items. Moreover, it provides an informative view for tracking the development's progression later on. Roadmap by www.storiesonboard.com Q1 Q2 Q3 Q4 TEAM 1 TEAM 2
  • 4. Purpose of roadmap As above described, roadmaps are helpful when you plan a new product or new features for a running product. Steps could be the followings: 1 Create a roadmap and create a card for each product component (or feature idea) Have a prioritization session and decide what's going to be developed first Detail the top-priority items by mapping out the user journey on a story map (or extend your product's story map with the new epic) Arrange/schedule the rest of the roadmap items Invite stakeholders to the roadmap Roadmaps are also useful when you have already done the story mapping session and the releases are scheduled. In this case, the roadmap provides a convenient board to track the development's progression. The steps are the following: Pick a roadmap template that suits your needs Decide how to group the items into columns eg: Q1 - Q2 - Q3 or NOW - NEXT - LATER Link a story map (or multiple story maps) to the roadmap Import story map items (Hint: use the quick-add option when creating the roadmap) Invite stakeholders to the roadmap 2 3 4 5 1 2 3 4 5 www.storiesonboard.com You’ve got a question? Let’s discuss how we can help you Book a demo
  • 5. How to pick the right roadmap template www.storiesonboard.com 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. Roadmap by In order to select the right roadmap template you should answer the following questions: How features or epics are grouped on your story map? Are you working in quarterly time-boxes or just picking backlog items from the top of the backlog? Should you share everything from your story map? 1 2 3 Build your own product roadmap Try Roadmap
  • 6. How to pick the right roadmap template How features or epics are grouped on your story map? 1 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. Are you working in quarterly time-boxes or just picking backlog items from the top of the backlog? 2 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. www.storiesonboard.com There are multiple ways to set up the column structure on the roadmap. Here are the most popular structures:
  • 7. How to pick the right roadmap template Should you share everything from your story map? 3 www.storiesonboard.com 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. Product roadmap templates on StoriesOnBoard 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. 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, and everything is managed within the same story map. Release roadmap Learn more
  • 8. How to pick the right roadmap template 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. If you grouped features into large business releases across multiple story maps, this template is for you. Create a high-level overview of your initiatives on a single roadmap and track progression effortlessly. www.storiesonboard.com Epic roadmap Portfolio roadmap Learn more Learn more
  • 9. How to pick the right roadmap template High-level roadmaps allow you to visualize large-backlog items from multiple story maps on an easy-to-understand board. You can group roadmap items with swimlanes for a better visuality. High-level roadmap Create a custom roadmap with items created from scratch. This roadmap type allows you to create visualize high-level or company initiatives. Single roadmap www.storiesonboard.com Product Roadmap Connect to Story Maps & Releases Start FREE Trial Learn more Learn more
  • 10. www.storiesonboard.com Product Management on StoriesOnBoard StoriesOnBoard is a lightweight product management tool built around user story mapping. A visual, intuitive, and collaborative solution for product managers to put customer value first. You’ve got a question? Let us know and let’s discuss what are the best practices. Start FREE Trial End-to-end product management Build lovable products together from idea to reality www.storiesonboard.com