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.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
Planning a platform backlog
Key decisions
- Measure: Use completed story points for capacity discussion.
- Comparison: Show commitments beside outcomes.
- Trend: Review multiple sprints rather than one result.
When to reuse this
Use this chart within one team to support sprint planning and retrospective discussion.
Frequently asked questions
What is sprint velocity?
Why show committed points too?
Can teams compare velocity?
Tweak it with chat, export PNG/SVG, or fork it for your own use case.