Honest Roadmaps
A method developed by group of software development experts to build predictable and reliable roadmaps
What This Method Gives You
Prevent Delivery Slips
Stop struggling with missed deadlines and budget overruns.
Proven Techniques,
Unique Toolset
Leverage established tools to drastically reduce roadmap errors and uncertainty.
Evidence-Based Roadmaps
Implement a usable process designed for companies that value realistic planning.
The Method
Steps to Build and Maintain an Adaptive Roadmap
Based on Delivery Simulations
Build the Portfolio
The portfolio defines the signals worth exploring. A signal, is defined as hypothesis (initiative) being worth investment and testing. Once enough information about a particular signal is collected, it can be either reinforced or cancelled to leave opportunity for new developments.
Features inside initiatives represent underlying business ideas. Each feature or subset of features could be prioritized against their potential ROI using different product management frameworks (such as RICE, Kano, etc).
Collect the Data
All requirements, high-level estimates, dependencies and other inputs related to features and initiatives should be carefully collected, verified with teams, and recorded for current and future reference. Some technical inputs, such as high-level estimates, must include a level of uncertainty and assumptions. The data shouldn’t necessarily be 100% or even 50% complete, but if there is any level of risk or uncertainty, it must be recorded.
Do the Delivery Simulation
Once the data is available, the next important step is delivery simulation and sequencing. All data pieces must be evaluated:
- Which scope do we assume for each feature?
- Which teams will be performing the features?
- Are there any dependencies?
- What is the risk buffer? How does the buffer correlate with uncertainty and risk appetite?
- How calendar days allocated for the tasks relate to the teams’ availability and velocity?
The tool Deep Planner built in-house can help build and fine-tune the delivery simulation with the help of automation.
Perform Alignment
Developers, stakeholders, managers and other parties must be invited into the roadmap alignment. There could be multiple rounds of reviews where parties will be able to verbalize gaps in data, scope preferences, or claim ownership of features. This is also a good time to reassess the portfolio hypothesis in case it wasn’t proven practical. A properly aligned roadmap serves both as a proof of portfolio visibility and an execution strategy.
Execute and Track Status
The roadmap can be executed using normal short development cycles, like sprints. Measuring the portfolio progress should be connected to measuring the progress and completion status of the underlying initiatives, features, and their dependencies. This should be an ongoing and frequent process—ideally, synced to the short development cycles—to address the potential risks and make any necessary adjustments early. To update the roadmap, follow the same steps, starting from updating the portfolio inputs, and proceed downstream.