Agile Velocity Calculator for Sprint Planning and Forecasting

Calculator Inputs

Completed Story Points per Sprint

Comma or line separated. Example: 24, 28, 31, 26

Committed Story Points per Sprint

Optional. Used for predictability analysis.

Team Capacity Days per Sprint

Optional. Helps normalize velocity by available effort.

Sprint Labels

Optional. If omitted or mismatched, default sprint labels are generated.

Remaining Backlog Points

Optional. Used for delivery forecasting.

Rolling Average Window

Common choice: 3 sprints.

Sprint Length in Weeks

Used to convert forecast sprints into weeks.

Confidence Buffer %

Applies optimistic and conservative forecast spread.

Next Sprint Capacity Days

Optional. Converts average points per day into a next sprint estimate.

Formula Used

Velocity: Velocity = Completed story points in a sprint.

Average Velocity: Average velocity = Sum of completed story points ÷ Number of sprints.

Rolling Average: Rolling average = Sum of the latest sprint velocities in the chosen window ÷ Window size.

Predictability: Predictability % = Completed story points ÷ Committed story points × 100.

Points per Capacity Day: Points/day = Completed story points ÷ Team capacity days.

Forecast Sprints: Sprints needed = Remaining backlog points ÷ Forecast velocity, rounded up.

Consistency Score: Consistency score = 100 − (Standard deviation ÷ Average velocity × 100), with a minimum of zero.

How to Use This Calculator

Enter completed story points for at least two sprints.
Add committed story points if you want predictability analysis.
Enter capacity days if staffing or availability changes matter.
Set the rolling average window, sprint length, and confidence buffer.
Add remaining backlog points to estimate future delivery timelines.
Click Calculate Velocity to show results above the form.
Review the graph, sprint table, forecast scenarios, and summary metrics.
Use the CSV or PDF buttons to export the current analysis.

Example Data Table

Sprint	Completed Story Points	Committed Story Points	Capacity Days
Sprint 1	24	30	40
Sprint 2	28	32	40
Sprint 3	31	35	42
Sprint 4	26	30	38
Sprint 5	34	36	40
Sprint 6	30	33	41

FAQs

1) What does agile velocity measure?

Agile velocity measures how many story points a team completes in one sprint. It helps engineering teams estimate future delivery using actual historical output instead of guesses.

2) Why should I use a rolling average?

A rolling average reduces the effect of one unusually high or low sprint. It gives a steadier planning baseline when staffing, bugs, support work, or sprint scope varies.

3) Is higher velocity always better?

Not always. A higher velocity can be useful, but unstable velocity may signal inconsistent scope, changing estimation habits, or uneven delivery conditions. Reliability often matters more than one large sprint.

4) What is predictability in this calculator?

Predictability compares completed points with committed points. A higher percentage means the team usually finishes what it planned, which improves release confidence and stakeholder communication.

5) Why include capacity days?

Capacity days help adjust expectations when team availability changes. If holidays, on-call work, or leave reduce engineering time, a capacity-adjusted forecast can be more realistic than raw velocity alone.

6) How many sprints should I include?

Three to six recent sprints often provide a practical starting point. Include enough data to capture normal variation, but avoid very old sprints that no longer reflect the current team.

7) Can this calculator estimate a release date?

Yes. Enter the remaining backlog points and sprint length. The calculator estimates optimistic, likely, and conservative timelines in both sprints and weeks for planning discussions.

8) Should velocity be compared across different teams?

Usually no. Story points are team-specific, so cross-team velocity comparisons can mislead. Use velocity mainly to improve each team’s own planning, forecasting, and learning over time.