Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile Product Roadmaps


Published on

This slide deck discusses what a product roadmap is, the benefits it offers, and how you can effectively apply it in an agile, Scrum-based context.

Published in: Business
  • Login to see the comments

Agile Product Roadmaps

  1. 1. © 2016 Pichler Consulting Ltd Agile Product Roadmaps Roman Pichler @romanpichler
  2. 2. © 2016 Pichler Consulting Ltd About Roman • Product management consultant, teacher, and author – 15 years experience in teaching and coaching product managers and helping companies establish an effective product management function – Specialised in agile and in lean practices • Business owner and product manager – I try to walk my own talk Product Strategy and Product Roadmap Practices for the Digital Age STRATEGIZE ROMAN PICHLER My books
  3. 3. What is a product roadmap?
  4. 4. Source: Google Maps
  5. 5. The Product Roadmap Defined • A product roadmap is an actionable plan that shows how a product is likely to evolve. • It typically covers several major releases or product versions. © 2016 Pichler Consulting Ltd
  6. 6. Roadmap Benefits • Provides a continuity of purpose • Facilitates stakeholder collaboration • Helps with prioritisation • Unburdens the product backlog • Helps acquire a budget • Supports portfolio management © 2016 Pichler Consulting Ltd
  7. 7. My Roadmapping Tips
  8. 8. Focus on Goals, not Features The release date or timeframe. The reason for creating the new release. The metrics to determine if the goal has been met. Goal Date Metrics The name of the new major release.Name The high-level features necessary to meet the goal.Features © 2016 Pichler Consulting Ltd
  9. 9. Product Roadmap Strategic plan: describes how the product is likely to grow across several product releases. Tactical tool: provides the details, including epics and user stories, that have to be implemented to create one or more releases. Product Backlog Derive the Product Backlog from the Roadmap © 2016 Pichler Consulting Ltd
  10. 10. Do the Necessary Prep Work © 2016 Pichler Consulting Ltd Realistic Product Roadmap Validated Product Strategy
  11. 11. Roadmap with the “Players” © 2016 Pichler Consulting Ltd High Interest Low Interest High PowerLow Power Crowd Context Setters Subjects Players Source: C. Eden and F. Ackermann, Making Strategy.
  12. 12. Decide Who Owns the Roadmap Product Manger/Owner Development Team Users and Customers Marketer Service and Support Management Sponsor Sales Rep Product Manager/Owner of a Related Product Product Roadmap When an external roadmap is used. 13© 2016 Pichler Consulting Ltd Owns the roadmap
  13. 13. Determine Cost Top-Down 14 How many people with which skills? Rough Estimate, Ballpark Figure Product Roadmap If cost is too high or people are unavailable: adjust roadmap or pivot. © 2016 Pichler Consulting Ltd
  14. 14. Regularly Review the Roadmap © 2016 Pichler Consulting Ltd Mature product Young product Stable marketDynamic market Review monthly Review quarterly Review quarterly Review every 3 to 6 months
  15. 15. The End.
  16. 16. You can find more information at: Thank You! © 2016 Pichler Consulting Ltd I look forward to your questions: @romanpichler