Release Planning

Purpose

Release Planning bridges the gap between the product vision and Sprint-level execution. The team maps features to iterations, balances scope with capacity, and produces a release plan that stakeholders can rely on for business planning.

At a glance

How to run

1. Confirm the release goal (10 min) — What must be true for this release to be successful?
2. Review velocity/throughput (10 min) — Share the team's historical delivery rate.
3. Feature overview (15 min) — Product Owner presents the prioritized feature list with estimates.
4. Map to iterations (40 min) — Place features into iteration slots based on priority, dependencies, and capacity. Leave buffer (15–20%) for unplanned work.
5. Identify risks (15 min) — What could derail the plan? Technical risks, dependencies, holidays, people changes.
6. Confidence vote (5 min) — Fist-of-five. If below 3, adjust scope or timeline.
7. Communicate the plan (15 min) — Summarize the release plan, milestone dates, and assumptions. Share with stakeholders.
8. Close (10 min) — Agree on cadence for plan reviews (every Sprint or monthly).

Materials needed

• Feature list with estimates
• Velocity or throughput data
• Release calendar (iterations, holidays, dependencies)
• Release plan template (board or spreadsheet)
• Risk register

Pitfalls & common mistakes

• No buffer — 100% capacity allocation guarantees missed dates. Include 15–20% buffer.
• Plan treated as commitment — A release plan is a forecast, not a promise. Update it regularly.
• Missing stakeholders — Business stakeholders must participate to validate scope and dates.
• Never updating the plan — Review and adjust every Sprint based on actual progress.

Inclusion & accessibility

• Share the feature list and velocity data 48 hours before.
• Use a visual board so all participants can see the plan taking shape.
• Ensure remote participants have equal access to the board.

Variations

• Quarterly planning — Plan for a quarter rather than a single release.
• Theme-based planning — Group features by theme and assign themes to iterations.
• Probabilistic planning — Use Monte Carlo simulation to forecast release dates with confidence intervals.

When NOT to use this

• If the team ships continuously (CD) without release trains — use feature toggles instead.
• If scope and date are both fixed — the plan becomes fiction. Negotiate one variable.

Source & further reading

• Cohn, M. (2005). *Agile Estimating and Planning*. Prentice Hall.
• Rubin, K. (2012). *Essential Scrum*. Addison-Wesley.