Roadmaps are probably one of the most used Product artifacts. All your stakeholders are looking at the Roadmap. Sales wonders if the promised features will be part of the deliveries. Support is looking if the quality issues are being solved, development is concerned about the technical debt, and management is wondering, "Is that all?". The friendliest stakeholder is mostly your customers.
And then we know that everything is changing. New requirements enter the backlog, and some planned issues take a longer time than anticipated. Your stakeholders are bound to be upset. Suddenly we are spending a lot of time in Expectation Management.
Expectation Management is difficult and important.
But the solution might be in the structure of the Roadmap. Can we create a Roadmap that is more durable and useful even when things change?
Daniel Zacarias shared his concept on Elastic Roadmaps that provides a more resilient Roadmap. A roadmap based on outcomes, not output.
In addition to the presentation from Daniel the following tools are relevant:
Roadmap & PieChart a winning combination
#23 Roadmap - How to create valuable Roadmaps
#14 Pie Chart Prioritization - Grok The logic and Pie Chart and Lead your product!
Requirement models and prioritization
#37 Requirement Priniciples - a checklist to evaluate and design your requirement management
#36 RICE Prioritization - a tool to evaluate and prioritize requirements
#35 MoSCoW Prioritization - A tool for grooming your backlog
#34 Buy-a-Feature - A fast and engaging way to prioritize development
#4 Opportunity Scoring - Prioritization tool for Outcome driven Innovatio