Enter Story Points Completed

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

Sprint 1:

Sprint 2:

Sprint 3:

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

Frequently Asked Questions

What is a good sprint velocity? ▼

There is no universal "good" number: velocity is relative to your team's estimation scale. As a rough reference band, a 3-developer team using standard Fibonacci-style points often lands at 20-40 points per 2-week sprint once estimation is stable. What matters more than the absolute number is consistency across sprints (low variance) and whether you can commit to and finish that amount reliably.

How do I calculate story point velocity? ▼

Sum the story points completed (Done, per your Definition of Done) across your last 3-5 sprints, then divide by the number of sprints. That average is your velocity. Enter each sprint's points in the calculator above and it does the math plus surfaces min/max and a suggested commitment at 80% of average for a safe buffer.

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 5,204 product managers and see how easy it is to build products people love.