Sprint Velocity Calculator

Calculate your team's average velocity for better sprint planning

Enter Story Points Completed

Add the story points completed in each of your past sprints.

What is Sprint Velocity?

Sprint Velocity is the average number of story points (or other units) a team completes during a sprint. It's used in Agile/Scrum for capacity planning and forecasting.

Formula:

Velocity = Total Points Completed / Number of Sprints

Best Practices:

  • Use at least 3-5 sprints for a reliable average
  • Exclude anomalies (holidays, team changes)
  • Don't compare velocity between teams
  • Commit to 80-90% of average for safety

What affects velocity?

  • Team composition changes
  • Technical debt/infrastructure work
  • Sprint length consistency
  • Estimation accuracy improvements

Prioritization Tools

WSJF Calculator RICE Calculator ICE Calculator MoSCoW
View all tools →

Frequently Asked Questions

How many sprints should I use for velocity? ▼
Use at least 3 sprints, ideally 5-6 for a stable average. Too few sprints give unreliable data; too many may include outdated data from before team changes. Some teams use a rolling average of the last 3-4 sprints.
Should I include partially completed stories? ▼
No - only count stories that are fully "Done" according to your Definition of Done. Partially completed work carries over to the next sprint. This keeps velocity honest and predictable.
Why shouldn't I compare velocity between teams? ▼
Story points are relative measures unique to each team. A "3-point" story for Team A is different from Team B. Comparing velocities creates unhealthy competition and gaming of estimates. Velocity is for internal planning only.
What if velocity varies a lot between sprints? ▼
High variance suggests: inconsistent sprint lengths, varying team capacity (PTO, holidays), changing scope mid-sprint, or inconsistent estimation. Focus on stabilizing these factors. Use your minimum velocity for conservative planning.
How do I use velocity for release planning? ▼
Estimate total story points for your release, divide by velocity to get estimated sprints needed. Add 10-20% buffer for unknowns. Example: 100 points at 20 velocity = 5 sprints, plus buffer = 6 sprints.

The faster, easier way to capture user feedback at scale

Join over 3,051 product managers and see how easy it is to build products people love.

Aaron Dye Timothy M. Ben Marco Chris R.
from 124+ reviews
ProductLift dashboard preview ProductLift dashboard preview

Did you know 80% of software features are rarely or never used? That's a lot of wasted effort.

SaaS software companies spend billions on unused features. In 2025, it was $29.5 billion.

We saw this problem and decided to do something about it. Product teams needed a better way to decide what to build.

That's why we created ProductLift - to put all feedback in one place, helping teams easily see what features matter most.

In the last five years, we've helped over 3,051 product teams (like yours) double feature adoption and halve the costs. I'd love for you to give it a try.

Ruben Buijs, Founder
Ruben Buijs

Founder & Digital Consultant