Agile planning

Sprint Velocity Calculator

Enter the story points your team committed and completed in past sprints to see average velocity, consistency and trend, then forecast when the remaining backlog will be done.

SprintCommitted ptsCompleted pts
-Average velocity (points per sprint)
-Last 3 sprints avg
-Median velocity
-Min - max
-Std deviation
-Say/do ratio
-Trend per sprint
CommittedCompletedAverage

Backlog forecast

ScenarioVelocity usedSprints neededWeeksProjected finish

Optimistic uses the average of your best three sprints, pessimistic the average of your worst three (or the max and min with fewer sprints).

Runs entirely in your browser. Nothing is uploaded to any server.

Why track sprint velocity

Plan realistic sprints

Commit to what the team actually delivers, not what it hopes to deliver.

Forecast with ranges

Best, likely and worst-case velocities give stakeholders honest dates.

Spot instability

High deviation or a low say/do ratio points to estimation or scope issues.

How to calculate sprint velocity

  1. Enter past sprintsAdd each sprint's committed and completed story points, or load the example.
  2. Read the statsSee average, rolling and median velocity, consistency and the trend line.
  3. Forecast the backlogEnter remaining points and sprint length to project sprints, weeks and a finish date.

What is sprint velocity?

Velocity is the amount of work a scrum team completes in a sprint, usually measured in story points. Only fully finished work counts, so a story that is 90% done adds nothing until it is accepted. Averaged over several sprints, velocity becomes a planning tool for how much the team can pull into the next sprint and how long a backlog will take.

Because velocity swings with holidays, sick days and unexpected work, a single number can mislead. This calculator shows the median and the last three sprints alongside the average, plus a range forecast based on your best and worst sprints.

Average velocity

Total completed points divided by the number of sprints.

Say/do ratio

Completed divided by committed points. Around 80 to 100% is healthy.

Sprints needed

Remaining backlog divided by velocity, rounded up to whole sprints.

Sprint velocity FAQ

How many sprints do I need for a reliable velocity?

Three to five sprints give a useful average. Teams that just formed or changed members should expect it to move.

Should unfinished stories count toward velocity?

No. Only stories that meet the Definition of Done count. Carry unfinished stories to the next sprint and count them when they are done.

Can I compare velocity between teams?

It is not recommended. Story points are relative to each team, so velocity is only meaningful within the same team.

What is a good say/do ratio?

Most teams aim for 80% to 100%. Consistently lower values suggest over-commitment or unplanned work.

Is my data saved?

Your sprints are saved in this browser only so they are there next time. Nothing is uploaded.

Try other agile tools

More free tools from My Panda Toolbox.

KANKanban BoardOrganize work in columns. RETRORetrospective BoardRun a sprint retro. STNDStandup Notes GeneratorWrite standup updates. GNTTGantt Chart BuilderPlan project timelines.