Release Team Velocity Chart

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.

類型 長條圖引擎 echarts-bar更新時間 2026/9/24

需求

“Create a velocity chart for the Release Team showing planned and completed story points for Sprints 5 to 10: 18/17, 20/19, 21/20, 19/18, 22/21, and 20/20.”

接著試試Add a release target of 120 completed points.Change Sprint 9 planned points to 20.

這張圖裡有什麼

看懂背後的決策。

01Trend

Use several completed sprints for the forecast.

02Commitment

Note the gap between planned and completed work.

03Release scope

Convert the forecast into a range, not a promise.

Use this chart for a single delivery team forecasting its share of a release backlog.

瀏覽所有長條圖範本 →

常見問題

How does velocity help release planning?

Recent completed velocity can support a range estimate for how much of a backlog one team may finish over future sprints.

Why use completed work?

Completed work reflects items that met the team's definition of done, rather than work merely started.

What is a velocity range?

It is a realistic lower-to-upper planning band based on recent variation rather than one fixed number.