Free Agile Tool

Sprint Velocity Calculator

Enter your completed story points per sprint to calculate your team's velocity and project your backlog completion.

Sprint History

3 sprints

Velocity Stats

Enter story points above to see velocity stats.

Backlog Projection

Remaining story points in backlog

Leave blank to skip projection estimates.

Add sprint data and a backlog size to see projections.

Ready to estimate your next sprint?

What is Sprint Velocity?

Sprint velocity is the amount of work a scrum team completes during a single sprint, measured in story points. It is calculated by averaging the story points completed across multiple historical sprints. Teams use velocity as a planning tool — not a performance metric — to forecast how much backlog they can realistically deliver in upcoming sprints.

A stable, well-understood velocity helps scrum masters and product owners set realistic expectations with stakeholders, prioritize the backlog effectively, and plan for release dates. This calculator gives you average, median, best-case, and worst-case velocities so you can build robust projections rather than relying on a single number.

Frequently Asked Questions

How many sprints do I need to calculate a reliable velocity?

Most agile coaches recommend at least 3 to 5 completed sprints before treating velocity as reliable. Fewer sprints produce a meaningful estimate, but the margin of error is higher. The more data points you add, the more accurate your average becomes — outlier sprints (holidays, team changes) affect the number less over time.

What is the difference between average and median velocity?

The average (mean) sums all sprint point totals and divides by the number of sprints. One unusually high or low sprint can skew it. The median is the middle value when sprints are sorted — it is more resistant to outliers. For teams with volatile sprints, the median often gives a more realistic planning baseline than the average.

Should I use best-case or worst-case for release planning?

For stakeholder commitments, use the worst-case (minimum velocity) estimate to set a conservative deadline. Internally, the average gives the most likely scenario. Sharing a range — "between X and Y sprints" — is more honest than a single number and builds trust. Avoid committing only to the best-case scenario unless you have strong reasons to believe performance will remain at its peak.

Estimate your next sprint with your team

Once you know your velocity, use Planning Poker to size upcoming backlog items accurately — all for free, no account required.

Join a Session

Create a Session