What is velocity in agile project management?
Velocity is a metric in Scrum that shows how many story points a team completes on average per sprint. It serves realistic planning, not measuring individual performance.
DEFINITION
Velocity describes the average amount of work a Scrum team completes within a sprint, measured in story points. It is not invented on a whiteboard — it comes from real sprint values. After several sprints, a stable pattern emerges that predicts how much work the team can realistically deliver in the next sprint. Velocity is a planning tool, not a prestige measure. It says nothing about whether a team works well or poorly, because story points are team-specific units that cannot be compared between teams. Using velocity to compare teams or apply pressure destroys its only sensible use: honest planning. When a team’s velocity drops, that is an early indicator of problems such as unclear requirements, dependencies, or too much parallel work.
CONNECTIONS
Leadership
Genuine delegation increases velocity: when leaders actually hand over decisions and do not require sign-off on every small matter, fewer blockers arise and throughput increases.
Artificial Intelligence
Machine learning can improve velocity forecasts by evaluating patterns from past sprints (complexity, disruptions, team size) and delivering more realistic capacity estimates.
Project Management
Velocity affects the critical path in an agile context: when a team delivers significantly fewer points than estimated, the completion date shifts, which affects milestones and dependencies.
KEY POINTS
- Velocity measures story points per sprint, not hours or output volume.
- It stabilises after several sprints and enables forecasts.
- Velocity is not a benchmark between teams.
- Falling velocity signals systemic team problems early.
- Artificially inflated velocity through story-point inflation destroys its value.
EXAMPLE
A five-person development team completes an average of 42 story points in the last four sprints. Velocity is therefore 42. Based on that, the Product Owner plans which backlog items are realistically achievable in the next sprint and does not promise more than 42 points. The team delivers on time without stress.
MISCONCEPTIONS
Can I use velocity to compare teams?
No. Story points are team-specific and not standardised. A team with velocity 80 is not necessarily twice as productive as one with 40.
Should I raise velocity by assigning more story points?
No. That is called story-point inflation and destroys the metric’s usefulness. Velocity serves honest planning, not appearances.