Sprint Velocity measures the amount of work a development team completes per sprint, typically in story points. It is the most reliable metric for sprint capacity planning when averaged over 3-5 sprints. The formula is Velocity = Total Story Points Completed / Number of Sprints. A good benchmark is stable velocity (less than 20% variance) indicates a mature, predictable team. PM Toolkit's free velocity calculator helps product managers plan sprint capacity with multi-sprint tracking with running average, variance analysis, and capacity forecasting.
Ask Claude, Cursor, or ChatGPT to run this calculator.
This calculator isn't in MCP yet — but install once for 17 others your AI can call.
Sprint Velocity Calculator
Track team delivery capacity with statistical confidence — predict when work will ship, not when you hope it will.
Updated
Ready
AvgVelocity = mean(CompletedPoints[]) over RollingWindow sprints
Rolling window smooths short-term noise. Use percentiles for commitments — averages hide variability.
What is Sprint Velocity?
Sprint velocity measures how much work an agile team completes per sprint, typically measured in story points. It's not about speed but predictability - a team delivering 30 points consistently is more valuable than one varying between 20-60 points. Use our free velocity calculator to track team performance with confidence intervals and make data-driven sprint commitments.
How to Calculate Sprint Velocity
- Collect story points completed for each sprint over the last 6-10 sprints
- Calculate the average (mean) velocity across these sprints
- Calculate the standard deviation to understand variability
- Use the P85 velocity (85th percentile) for sprint planning instead of the average
- Monitor trends and team health metrics for early warning signals
Industry Benchmarks for Sprint Velocity
Small Teams (3-4 devs)
20-35 points
Per 2-week sprint
Medium Teams (5-7 devs)
35-60 points
Per 2-week sprint
Large Teams (8-10 devs)
50-80 points
Per 2-week sprint
Individual Productivity
8-12 points
Per developer
Benefits of Velocity Tracking
Predictable Planning
Make realistic commitments with confidence intervals and historical data.
Early Warning System
Detect team health issues before they impact delivery timelines.
Stakeholder Alignment
Set realistic expectations with data-driven delivery forecasts.
Continuous Improvement
Identify patterns and optimize team performance over time.
Common Velocity Calculation Pitfalls
❌ Using velocity to compare teams
Creates perverse incentives and gaming behaviors that reduce actual productivity.
Use velocity for individual team planning and improvement only
❌ Pressuring teams to increase velocity
Leads to story point inflation and technical debt accumulation.
Focus on consistency and removing impediments instead
❌ Planning with average velocity
Results in 50% sprint failure rate and broken commitments.
Use P85 velocity for commitments to achieve 85% success rate
An Illustrative Example
Planning with P85 instead of the average
Picture a squad that commits to its average velocity every sprint and misses the goal about half the time. The average ignores how much the team's output swings from sprint to sprint, so it over-promises whenever a sprint runs light.
Switching the commitment to the P85 velocity (the level the team has hit or beaten in 85% of past sprints) builds the team's own variability into the plan. The committed number drops, but the team starts hitting it. Stakeholders get releases they can count on, which usually matters more than a higher headline number.
Key insight: consistency beats speed. A predictable 25 points you can plan around is worth more than a volatile 30 you cannot.
Rate this calculator:
Velocity benchmarks by team size
| Segment | Benchmark |
|---|---|
| Small Team (3-4 devs) | 20-35 points/sprint |
| Medium Team (5-7 devs) | 35-60 points/sprint |
| Large Team (8-10 devs) | 50-80 points/sprint |
| Velocity per Developer | Not a meaningful benchmark |