Agile Release Planning and Product Roadmaps: Planning Without Pretending to Predict

New Scrum Masters are often surprised by the question that arrives within the first week: "That's nice, but when will it be done?" Scrum plans in detail only one Sprint ahead, yet organisations need to plan budgets, marketing launches and dependencies months in advance. Agile does not ban longer-term planning. It changes the way planning is done: lighter, more flexible, outcome-oriented and updated as knowledge grows. This lesson covers roadmaps, release planning and the tools that help teams answer date questions without false promises.

Planning Horizons in Agile

Think of planning as a series of horizons, each with a different level of detail.

HorizonTypical timeframeArtifactLevel of detail
Vision and strategy1 to 3 yearsProduct visionVery broad
Roadmap3 to 12 monthsProduct roadmapThemes and outcomes
Release plan1 to 3 monthsRelease forecastFeatures, grouped by priority
Sprint1 to 4 weeksSprint Goal and Sprint BacklogDetailed work items
Day24 hoursDaily Scrum planSpecific tasks

The farther into the future, the less detail and the more uncertainty. Pretending otherwise creates plans that look precise and are wrong.

The Product Roadmap

A product roadmap communicates direction: where the product is heading and why. A poor roadmap is a Gantt chart of features with dates; teams are then held to dates that were guesses. A strong roadmap is built around outcomes and confidence.

Features of a good roadmap

  • Outcome-based. "Reduce time to first value for new users" rather than "build onboarding wizard".
  • Time-horizon buckets, such as Now, Next and Later, rather than precise dates for distant items.
  • Linked to the Product Goal. See Product Goal and Sprint Goal Examples.
  • Honest about uncertainty. Items further out are marked as hypotheses.
  • Living. Reviewed and updated regularly with evidence from users and the market.

A Now-Next-Later example

  • Now: Allow customers to track their order status in the app.
  • Next: Reduce support contacts about delivery delays.
  • Later: Explore proactive delivery notifications and partner integrations.

Release Planning

Release planning bridges the roadmap and the Sprint. Scrum does not prescribe a release planning event, but many teams use a regular session to look ahead a few Sprints. A simple approach:

  1. Clarify the release goal: what must be true for this release to be worthwhile?
  2. Review the ordered Product Backlog and identify the items needed for the goal.
  3. Estimate roughly using the team's existing sizing approach. See Estimation and Story Points in Scrum.
  4. Forecast using the team's history, using velocity or throughput. See Forecasting in Scrum and Agile.
  5. Express the result as a range, not a single date, and revisit it every Sprint.
  6. Agree what is flexible: scope, date or budget. Not all three can be fixed.

Fixed date, flexible scope

The most robust Agile approach to a hard deadline is to fix the date and flex the scope. Order the backlog so the most valuable items come first. As the date approaches, the least valuable items drop off. Stakeholders see progress every Sprint and can decide when "good enough" has been reached.

Story Mapping

User story mapping, popularised by Jeff Patton, is a technique for building a shared picture of the whole product and slicing releases. You arrange user activities horizontally in the order a user performs them, then break each into steps and stories arranged vertically by priority. A horizontal line across the map defines a release slice: the thinnest set of stories that lets a user complete the entire journey. This is a vertical slice at product level and a powerful antidote to a flat, endless backlog. See Splitting User Stories.

Answering "When Will It Be Done?"

This is where Scrum Masters and Product Owners earn their keep. A helpful response has four parts:

  1. Acknowledge the need. The stakeholder has a legitimate reason: budget, contracts or a launch.
  2. Offer a forecast with a range, based on data: "At our current pace we expect to complete the core scope between Sprint 8 and Sprint 10."
  3. Show what could change it: scope additions, dependencies and team changes.
  4. Offer options: reduce scope, add capacity where sensible, or move the date.

Never present a single-point date as a commitment unless the scope is truly fixed and well understood.

Release Burnup Charts

A burnup chart plots completed work against total scope over time. Because it shows scope as a separate line, it makes scope growth visible: a rising scope line explains why the "done" line has not reached it yet. This is more honest than a burndown, which can hide scope changes. See Sprint Tracking in Scrum.

Dependencies and Coordination

When several teams or external parties are involved, release planning must account for dependencies. Practical steps include mapping dependencies visually, aiming to remove them through architecture or team design, and agreeing regular synchronisation points. For many teams working together, see Scaling Agile Frameworks Compared.

Common Mistakes

  • Publishing a feature roadmap with dates, then treating slips as failures.
  • Planning every Sprint for the next six months up front.
  • Quoting velocity as a promise instead of a forecast.
  • Ignoring user and market feedback, so the roadmap never changes.
  • Letting the roadmap become a wish list owned by whoever shouts loudest.
Key takeaways
  • Agile plans at several horizons, with detail decreasing as time increases.
  • Outcome-based Now-Next-Later roadmaps are more honest than feature-date Gantt charts.
  • Forecast with ranges based on the team's actual history.
  • When a date is fixed, flex the scope and order by value.

Related Lessons