Stack Exchange Network
Stack Exchange network consists of 181 Q&A communities including
Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Project Management Stack Exchange is a question and answer site for project managers. It only takes a minute to sign up.
Sign up to join this community
Anybody can ask a question
The best answers are voted up and rise to the top
6 years, 11 months ago
My boss loves Gaant charts, because they give you a high level visual overview of the product roadmap.
The problem with Gaant, it is fixed time related and goes completely against the concept of the teams velocity which you only really find out once they start working on sprints.
How can I devise a product roadmap for a particular version of the product?
Apr 25, 2016 at 16:30
3,882 1 1 gold badge 23 23 silver badges 43 43 bronze badges
One approach I have seen used is to have a roadmap which has epics/features shown as circle or ovals whose size gives a rough indication of the work involved. There is either no time units indicated or at the most quarter years are shown.
The idea is to make it deliberately vague, but still give an indication of the possible order in which work will be done. The more precise the roadmap looks, the more people will interpret it as having fixed dates.
Even using this kind of visual roadmap is dangerous as it creates some expectation for delivery. I would deliver the roadmap with a clear message that as you are working in an agile fashion it is possible or even likely that the roadmap will change over time.
Apr 26, 2016 at 7:19
Barnaby Golden Barnaby Golden
19k 2 2 gold badges 16 16 silver badges 49 49 bronze badges
Your backlog combined with your velocity is a rough road map.
Next 1-3 Sprints - well defined and decomposed. We understand this and have some certainty.
Next 6 Months - Bigger rocks that we can long term for sat
6-12 months - Ideas (even bigger rocks)
12 months + - vision, direction
You can easily draw columns that are sprints and place the backlog you have for planning. Just remember that the further out you go the more uncertainty there is.
May 4, 2016 at 5:43
On approach that I have created is the
Lean Roadmap Model. It combines 2 product strategy theories, the Lean Analytics Stages Model and the Hooked Model.
This approach is useful if you are a startup, or if you are in the early stages of the product development.
Here the time and velocity variables are not taken into consideration. What is taken into consideration is how each improvement impacts the product.
Apr 26, 2016 at 8:37
11 3 3 bronze badges
do you use any tools for that?
Craft and it is a really good solution for Agile product management designed by product manager!
With Craft you can create visual roadmaps, which you can view by
single roadmap (in a variety of displays) and multi-product roadmap
The best part is that everything in Craft connects to form a whole product management process. So you can assign personas to story maps, connect tasks and items to sprints and versions at roadmap.
Jan 26, 2018 at 14:26
11 1 1 bronze badge
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our
Accept all cookies
Necessary cookies only