Upload
vokiet
View
273
Download
3
Embed Size (px)
Citation preview
Roman Pichler’s
Agile Product Roadmap Tutorial
Slide deck
© 2006-2014 Pichler Consulting Ltd 2
• Agile product management and Scrum consultant, trainer and author with over 10 years experience in – Teaching and coaching product managers, product owners, business
analysts, and project managers
– Helping companies apply agile prac?ces to achieve business success
• Business owner and product manager – I walk my own talk
About Roman
One of my books!
Introduction
© 2006-2014 Pichler Consulting Ltd 4
• A product roadmap is a high-‐level plan that shows how a product is likely to evolve.
• It typically covers several major releases or product versions.
What is a Product Roadmap?
© 2006-2014 Pichler Consulting Ltd 5
The Benefits of a Product Roadmap
Stakeholder alignment and collaboration
Prioritisation Continuity of purpose
Umbrella for the product
backlog
Helps with portfolio
management
© 2006-2014 Pichler Consulting Ltd 6
• View it as a hard-‐and-‐fast plan or a commitment. • Focus too much on features.
– Makes it hard to achieve agreement and the roadmap more vola?le.
• List largely unrelated features to please individuals. • Create a roadmap when you cannot look beyond the next major release.
Common Roadmap Mistakes
© 2006-2014 Pichler Consulting Ltd 7
• Crea?ng a realis?c roadmap when markets and technologies change frequently and unexpectedly.
• Building a longer-‐term plan when agile teams commit to no more than four weeks.
• Unclear how the product roadmap and the product relate. – Do they compete with or complement each other?
Agile Roadmap Challenges
Creating an Agile Product Roadmap
9 © 2006-2014 Pichler Consulting Ltd
Let’s Look at an Example
10 © 2006-2014 Pichler Consulting Ltd
How do We Get to the Roadmap?
Idea
? ?
Product Roadmap
11 © 2006-2014 Pichler Consulting Ltd
First Create and Validate a Product Strategy
Idea
Product Roadmap
Product Strategy
A plan with!goals, dates !and metrics!
Validated!Value prop & !
biz goals!
12 © 2006-2014 Pichler Consulting Ltd
The GO Product Roadmap
Date The launch date or timeframe
Name The name of the new product version or major release
Goal The reason for creating the new version
Features The high-level features necessary to meet the goal
Metrics The metrics/KPIs to determine if the goal has been met
How do we know the goal!has been met?!
What are its!key features?!
Why should!it be developed?!
What is!it called?!
When will !the release !
be available?!
13 © 2006-2014 Pichler Consulting Ltd
A Sample GO Roadmap
3rd quarter!
Version 1!
• Basic game functionality!
• Multiplayer!• FB integration!
Downloads: top 10 dance app!
4th quarter!
Version 2!
• Purchase dance moves!
• Create new dances!
At least 10% of users make one in-app purchase!
1st quarter!
Version 3!
• New characters and floors!
• Enhanced visual design!
Daily active players, session length!
2nd quarter!
Version 4!
• Street dance elements!
• Dance competition!
Downloads!
Acquisition: Free app!
Revenue: in-app purchases!
Retention! Acquisition: New segment!
14 © 2006-2014 Pichler Consulting Ltd
The GO Roadmap Template
Download at romanpichler.com/tools/product-
roadmap
15 © 2006-2014 Pichler Consulting Ltd
Tips for Creating the GO Roadmap
Tell a convincing and realistic story.
Have the courage to say no.
Keep your roadmap simple and easy to
understand.
Prioritise date vs. goal.
Derive features from goals. Use helpful metrics.
Choose a realistic timeframe.
Create buy-in by involving key stakeholders.
Determine the right innovation cadence.
16 © 2006-2014 Pichler Consulting Ltd
The Roadmap Creation Workshop
Marketer Sales Rep Mgmt Sponsor
Product Owner Dev Team Members
Involve key!
stakeholders!
2-4 hours!
Vision Board Validated!
Value prop & !biz model!
GO Roadmap
17 © 2006-2014 Pichler Consulting Ltd
The Roadmap and the Backlog
GO Product Roadmap
Details !for the next !
major release!
Goals!for several!
major releases!Strategic!
Tactical!
Product Backlog
Managing the Roadmap
© 2006-2014 Pichler Consulting Ltd 19
• Your roadmap is not a fixed plan; it will change. – New ideas come up, progress is not as an?cipated, the market and the compe??ve landscape change.
– The changes may be small or big.
• Regularly review and update your roadmap. – The more change and uncertainty there is, the more frequently you should you check your roadmap.
– Tip: Start with monthly reviews and adapt. – Involve development team members and key stakeholders to leverage their knowledge and to create buy-‐in.
Roadmap Review and Update
© 2006-2014 Pichler Consulting Ltd 20
• Incremental changes help you implement your exis?ng product strategy. This assumes that your strategy is valid.
• Examples are revising a goal, changing a date or a feature, and adjus?ng the metrics.
Incremental Changes
Adjust!
GO Roadmap
© 2006-2014 Pichler Consulting Ltd 21
• Big changes are needed when the strategy that was used to create the roadmap is no longer valid. – You want to address a new market segment and new needs, for
instance, or you experience a pivot.
• Your exis?ng roadmap is no longer valid.
Big Changes
Bigger Update or Pivot New or!
reworked!roadmap!
New or !changed!strategy!
22 © 2006-2014 Pichler Consulting Ltd
Roadmap Ownership
Product Owner
Development Team Members
Stakeholders
Contribute!
Contribute!Owns and!manages!
GO Roadmap
More Info
24 © 2006-2014 Pichler Consulting Ltd
Attend my Training Course
Register at http://www.romanpichler.com/training-courses/
Available!for onsite!delivery!
You can find more info on agile roadmaps at:!
romanpichler.com/tools/product-roadmap!
I look forward to your feedback and questions:!
@romanpichler!