Strategy to Stories: Aligning, Planning, Forecasting, and Tracking Continuously

  • The process is tedious and can consume significant numbers of people
  • Requires that all deliverables are defined and detailed enough for the teams to estimate them
  • Evaluating the impact of changes is very difficult and disruptive so plans tend not to be updated as changes occur
  • Teams don’t realize they are behind until it is very obvious
  • We don’t compare our plans to actuals to see how we can improve because information is scattered making it difficult to do an apples to apples comparison so the process rarely improves
  • Planning artifacts are static and provide value to a limited audience rather than all involved
  • No single source of truth. Information lives in multiple places making it cumbersome to update
  • Limited visibility and transparency as to how plans were created and validated
  • No big picture overview
  • Plans are deterministic rather than probabilistic so people take them as guarantees
  • Difficult to account for dependencies especially between other programs and portfolios
  • Doesn’t scale
  • Plans are not realistic or reliable due to all the above
Master Roadmap
  • Generate probabilistic data driven roadmaps that can provide for improved decision making
  • Roadmap items can be generated based on fixed dates and duration or forecasted durations based on number of issues and historical cycle times so you can account for any type of work
  • Drastically reduce the amount of time teams spend assembling or changing estimates via automated Monte Carlo simulation forecasting rather than using very subjective effort driven approaches
  • Roadmap items can be linked to Jira epics allowing the roadmap item’s start date, durations, and completion date to automatically be updated in near real-time based on the progress of the epic’s child issues
  • Provide a comprehensive portfolio or organization view via master roadmaps that aggregate any number of child team road maps
  • Forecast anywhere from epic(multiple stories/issues)level all the way up to strategic initiatives
  • Allow you to see how strategic and business goals align with actual execution at any level
  • Evaluate multiple planning scenarios quickly, cheaply, and accurately
  • Account for dependencies between roadmap items either within the team or with external teams in other roadmaps
  • Provide visual indicators when completion dates have slipped beyond key threshold dates
  • Highly configurable so the presentation can be tailored to each specific audience all coming from the same source of truth
  • Quickly and easily determine the schedule impact of changes to existing or new priorities, team changes, and/or new dependencies
  • It’s free!!!
Roadmap inputs
Resulting roadmap from the inputs above
6 team level roadmaps and a single master roadmap
Imported Roadmaps Configuration
Master Roadmap containing 6 team roadmaps




Enterprise Agile Software Development Chief Technology Officer @ V1 Sports

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

How to Install and configure Webmin on CentOS 8

Top 10 Flutter Widgets That You Should Know Know as a Flutter Developer

Understanding The Memory Model Of Golang : Part 2

Getting started with the PWA

Getting Started with GCloud SDK: Part 2

Data Analytics platform to track SaaS Usage & Billing —  Metered Billing

Introducing Ruby’s First Gemstone NFTs

6 Ways We Get Things Done with Python

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
Michael Boumansour

Michael Boumansour

Enterprise Agile Software Development Chief Technology Officer @ V1 Sports

More from Medium

Four Reasons to Build a Data Warehouse

When to use quantitative vs qualitative data

Call for Interviews with Data Product Managers

The Radhika Dutt Hypothesis: Vision-driven products have a clear reason for being