All about Product Roadmaps
19
All about Product Roadmaps The IT Performance Experts
-
Upload
intechnica -
Category
Technology
-
view
112 -
download
1
description
Every great product needs a clear, well-defined product roadmap. This Slideshare explains the whats, whys and hows of Product Roadmaps in plain English.
Transcript of All about Product Roadmaps
What is a Product Roadmap?
A high level vision of the future evolution of the product
Functionality The Product Roadmap includes…
Image: Deviantart /ssj5goku28
Effort Required
The Product Roadmap includes…
Release dates
The Product Roadmap includes…
Executives
See what functionality is still outstanding and the effort required to deliver
Sales & Marketing
See what functionality is coming in upcoming releases and shape efforts based on this
Development team
Understanding of future direction of product
End users
If roadmap made public
Who uses the
Product Roadmap?
Who manages the
Product Roadmap?
Roadmaps should be managed by the Product Owner
Executives
Strategic direction
Development team
Practicalities – complexities, pre-requisites
Sales & Marketing
Upcoming sales/marketing activities that will influence new functionality
End users
Target roadmap based on feedback from users
Who maintains the
Product Roadmap?
What appears on a
Product Roadmap?
Features! aka User Stories
Features are self contained, testable items of functionality that can be delivered in isolation that will
add value to a system
Features should be
1 – 5 days development
Anything bigger should be classed as an Epic and split into smaller
features before developing Epics are acceptable on a product roadmap as
low priority items
What makes a good Product Roadmap?
A good product roadmap is
D E E P
etailed appropriately
stimated
mergent
rioritised
Detailed Appropriately
All high priority features should be fully defined
Features should get less and less detailed as their priority decreases
All items on the roadmap should be estimated!
Estimates should be more accurate as items become higher priority
Estimated
Product Roadmap is a living document – should be constantly re-evaluated because of factors
Nothing set in stone until accepted into the sprint backlog
Product roadmap should be re-evaluated at least at the end of each sprint
Emergent
Prioritise based on…
Value
Requirement
Pre-requisite of other functionality
Timeliness
Features that would group well
together into a release
Practicalities
Prioritised Roadmaps should include the order in which
features are planned to be implemented
How is a roadmap displayed?
Split into functional areas
For each release, also display
• Name for the release
• Estimated release date
• Effort included in the release
Features can be colour coded based on
• Size / effort
• Feature type
Image: Flickr/Giorgio Montersino
intechnica.co.uk
@intechnica
PerformanceByDesign.co.uk
@PerformByDesign
The IT Performance Experts
