What Is Velocity?
Velocity is a measure of how much work a team completes in a single sprint, typically expressed in story points. It is a planning tool, not a performance metric. By tracking velocity over multiple sprints, teams can predict how much work they can commit to in future sprints and give stakeholders realistic timelines.
Why velocity matters
Without velocity, sprint planning is guesswork. Teams either overcommit (leading to rolled-over work and missed deadlines) or undercommit (leading to idle time and missed opportunities). Velocity provides a data-driven basis for answering “how much can we do next sprint?” The answer is: approximately what we did in the last few sprints.
Velocity also helps with longer-range planning. If the product backlog has 120 points of estimated work and the team's average velocity is 30 points per sprint, the PM can estimate roughly four sprints to completion. This is approximate, but it is far better than no estimate at all.
How velocity works
At the end of each sprint, add up the story points for all items that met the team's Definition of Done. Partially completed items do not count. This number is the sprint velocity. Track it over time and use the average of the last three to five sprints as the planning baseline for future sprints.
During sprint planning, use this baseline to set the sprint scope. If average velocity is 28 points, plan for 25 to 30 points. Leave a buffer for unplanned work. Over time, the team's velocity stabilizes and planning becomes more predictable.
Common mistakes
- Using velocity as a performance metric to evaluate or compare individual developers.
- Pressuring teams to increase velocity, which leads to estimate inflation rather than more work.
- Counting partially completed items, which inflates velocity and makes planning unreliable.
- Comparing velocity across teams with different calibrations.
- Ignoring velocity fluctuations instead of investigating what caused them.
Related terms
- Story Points
The estimation unit that velocity is measured in
- Sprint Planning
The ceremony where velocity data guides sprint scope decisions
- Kanban
Uses throughput and lead time instead of velocity for flow measurement
How Vantage helps
Vantage connects sprint execution back to product planning. When tickets sync from Linear or Jira, Vantage tracks which PRD requirements are being completed and how quickly. This gives PMs visibility into not just how fast the team is moving, but whether the velocity is directed at the right priorities.