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.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
Explaining velocity
Key decisions
- Unit: Use the team's own story points.
- Period: Label each sprint consistently.
- Trend: Compare several completed sprints.
When to reuse this
Use this basic velocity chart to explain a team's recent delivery pattern.
Frequently asked questions
What does a velocity chart show?
How many sprints should be shown?
Should velocity be a performance target?
Tweak it with chat, export PNG/SVG, or fork it for your own use case.