What Is Sprint Velocity?

Sprint velocity is a measure of how much work a team completes in a single sprint. It is typically expressed in story points or the number of completed items and is used to forecast how much work the team can take on in future sprints.

Why sprint velocity matters

Velocity gives product managers and engineering leads a data-driven way to plan. Instead of guessing how many stories fit into the next sprint, teams use their historical velocity to make realistic commitments. Over time, velocity also reveals trends. A steadily increasing velocity might indicate improved processes. A sudden drop could signal blockers, overcommitment, or context switching.

That said, velocity is a planning tool, not a performance metric. Using it to pressure teams into higher numbers leads to inflated estimates and gaming rather than genuine improvement. The most valuable use of velocity is honest, internal forecasting.

How to use velocity effectively

Track velocity over at least three to five sprints before using it to plan. A single sprint is noisy. A rolling average gives you a much more reliable picture of what the team can deliver. When planning a new sprint, use the average as a ceiling, not a target. Leave room for unplanned work and learning.

Pair velocity with other signals like cycle time (how long individual items take from start to finish) and carryover rate (how many items spill from one sprint to the next). Together, these metrics tell a fuller story about team health and predictability.

Related terms

• Sprint Planning

  The meeting where velocity data helps teams decide how much work to take on

• User Story

  The unit of work that gets estimated and counted toward velocity

• Product Ops

  The function that often owns velocity tracking and reporting