Release Team Velocity
This release-team velocity chart pairs planned work with completed work over six sprints. The close values suggest that the team's recent commitments are broadly aligned with delivery, but the chart should still be read as a range of capacity rather than a guarantee. Release planning can use the completed values to estimate when a backlog might fit, then adjust for dependencies and upcoming availability. The chart is most useful when the sprint length, estimation practice, and completion rules are consistent across the displayed period. It should stay with the team that created the estimates. Combining points from teams with different scales produces a misleading total.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
Forecasting a release window
Key decisions
- Trend: Use several completed sprints for the forecast.
- Commitment: Note the gap between planned and completed work.
- Release scope: Convert the forecast into a range, not a promise.
When to reuse this
Use this chart for a single delivery team forecasting its share of a release backlog.
Frequently asked questions
How does velocity help release planning?
Why use completed work?
What is a velocity range?
Tweak it with chat, export PNG/SVG, or fork it for your own use case.