Agile Velocity Calculator
Calculate your agile team's average velocity and forecast capacity for future sprints. Uses completed story points, sprint history, and capacity adjustments to produce a planning estimate.
About this calculator
Velocity is the average number of story points a team completes per sprint, measured over several sprints to smooth out outliers. The raw average is: averageVelocity = completedStoryPoints / numberOfSprints. This is then adjusted by a team capacity factor—a decimal representing the fraction of full capacity available in the upcoming sprint (e.g., 0.8 if a team member is on leave)—and a velocity trend multiplier that captures whether the team is improving or slowing: projectedVelocity = round(averageVelocity × teamCapacityFactor × velocityTrend). Using three to five sprints for the average is recommended because it balances responsiveness to recent changes with stability against single-sprint anomalies. Velocity should be used for planning, not as a performance metric.
How to use
A team completed 120 story points across 3 sprints, has a team capacity factor of 0.9 (one member at 50% for the sprint), and a velocity trend of 1.05 reflecting gradual improvement. Step 1 — Average velocity: 120 / 3 = 40 points/sprint. Step 2 — Apply capacity factor: 40 × 0.9 = 36. Step 3 — Apply velocity trend: 36 × 1.05 = 37.8. Step 4 — Round to nearest whole number: 38 story points. The team should plan approximately 38 points into the next sprint.
Frequently asked questions
How many sprints should I average to calculate a reliable agile team velocity?
Most Scrum practitioners recommend averaging 3 to 5 sprints for velocity calculation. Fewer than 3 sprints produces an unstable estimate that is highly sensitive to a single outlier sprint. More than 5 sprints may include data from when the team had different membership, tools, or processes, making it less relevant. If the team has recently changed significantly—new members, new tech stack, or new domain—it is better to treat them as a new team and reset the velocity baseline.
What does the team capacity factor represent in an agile velocity calculation?
The team capacity factor is a decimal between 0 and 1 that represents the proportion of normal working capacity available for the upcoming sprint. A value of 1.0 means the full team is available for the entire sprint. A value of 0.75 might reflect a sprint with holidays, a team member on leave, or significant non-project commitments like training. Multiplying historical velocity by this factor adjusts the sprint commitment downward to prevent over-promising and under-delivering.
Why should agile velocity not be used as a performance metric for comparing teams?
Velocity measures the rate at which a specific team completes its own story points, which are sized relative to that team's own reference stories. Different teams use different scales, different definitions of done, and have different types of work, making direct comparison meaningless. Using velocity as a performance metric creates incentives to inflate story point estimates, which destroys the calibration that makes velocity useful for planning. Velocity is a planning tool for a team to forecast its own future capacity, not a productivity benchmark.