ChatDiagram
agile · software

API Team Sprint Velocity

A velocity chart shows the amount of work a single agile team completes across successive sprints. In this example, the API Team's completed story points are displayed as one bar per sprint. The purpose is to observe a recent delivery pattern that can inform the team's own planning conversation. It is not a target for individuals and it should not be used to compare teams, because story points are local estimates rather than a universal unit of output. For a useful trend, keep the sprint duration and definition of done stable. Add commitment bars or an average line when the team needs to discuss planning accuracy or forecast capacity.

種類 棒グラフエンジン echarts-bar更新日 2026/9/24
API Team Completed Velocity
Drawing preview
依頼内容

“Create a velocity chart for the API Team showing completed story points for Sprints 41 to 46 of 26, 29, 27, 30, 28, and 31.”

次はこちらAdd a 29-point average line.Add Sprint 47 with 30 completed points.
この図に含まれるもの

図の背後にある意思決定を読み解く。

01Unit

Use the team's own story points.

02Period

Label each sprint consistently.

03Trend

Compare several completed sprints.

Use this basic velocity chart to explain a team's recent delivery pattern.

棒グラフのテンプレートをすべて見る →

よくある質問

よくある質問

What does a velocity chart show?

It shows a team's completed work across sprints, normally using that team's story-point estimates.

How many sprints should be shown?

Show enough recent sprints to see variation; six to ten is often a practical starting range.

Should velocity be a performance target?

No. It is a planning signal and can be distorted if treated as a target.