ChatDiagram
Kostenlos testen
agile · project-management

Platform Team Sprint Velocity

This velocity chart compares what a platform team committed to with what it completed over six sprints. The paired bars make it easy to discuss whether the team is planning close to its recent capacity and whether a particular sprint had an unusual result. Velocity is a local planning measure: its meaning depends on the team's own story-point scale, staffing, and definition of done. Use the chart to start a conversation about scope, interruptions, and delivery patterns. Do not use it to rank teams, because another team's estimates and working context are not directly comparable. Keep the work categories and sprint length consistent when reading a trend.

Typ BalkendiagrammEngine echarts-barAktualisiert 24.9.2026
Platform Team Velocity
Drawing preview
Die Anfrage

“Create a velocity chart for the Platform Team showing committed and completed story points for Sprints 21 to 26: 34/31, 36/33, 32/30, 38/35, 35/34, and 36/32.”

Dann probieren SieAdd a 34-point planning target line.Change Sprint 26 completed points to 36.
Was diese Zeichnung zeigt

Die dahinterstehenden Entscheidungen verstehen.

01Measure

Use completed story points for capacity discussion.

02Comparison

Show commitments beside outcomes.

03Trend

Review multiple sprints rather than one result.

Use this chart within one team to support sprint planning and retrospective discussion.

Alle Balkendiagramm-Vorlagen durchsuchen →

FAQ

Häufige Fragen

What is sprint velocity?

It is the amount of work a team completes in a sprint, commonly measured in that team's story points.

Why show committed points too?

The comparison helps the team see whether its planning assumptions are matching recent delivery.

Can teams compare velocity?

Usually not usefully, because each team estimates work and operates in a different context.