Serious Scrum
Published in

Serious Scrum

Why roadmaps reflect the level of Agile inadequacy

The Penguin Principle for Agile transformations

Picture by Marco Verch

What avians can teach us about roadmaps

Image by Markus De Nitto

Why do roadmaps reflect the level of Agile inadequacy?

“Employees rise to the level of their incompetence” — Laurence J. Peter

The Penguin Principle

“Roadmaps reflect the level of Agile inadequacy.”

  • What is the Product Vision for the overall roadmap?
  • What is the Product Strategy? What is the biggest challenge we’re facing, and what’s the most effective way to overcome this obstacle?
  • How was the roadmap created? Who was involved in the creation?
  • How were the different elements of the roadmap prioritized?
  • Is the roadmap feature-based or goal-based? Is it rooted in customer problems, pain points, wants, needs, struggles, or jobs-to-be-done?
  • How are timelines represented? Is it now, next, later? Is it in quarters? Or is it per month?
  • How were these timelines estimated? How much time is spent to achieve this (less is better)?
  • How far into the future does the roadmap cover?
  • Does every team have its own roadmap? Or is there an overall roadmap for the different teams?
  • How are prioritization conflicts between teams handled?
  • What features or goals did not make the roadmap? How was this decided?
  • How flexible is the roadmap? How will you deal with emergent understanding, failure, and learning?
  • Is the roadmap focused on delivery, or does it include discovery and validation?

Use the Penguin Principle for roadmaps

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store