Sprint Velocity Calculator

About the Sprint Velocity Calculator

Sprint velocity is the average number of story points a team completes per sprint. It is the primary metric for forecasting how long remaining work will take and for planning realistic sprint commitments. Accurate velocity tracking is the backbone of predictable agile delivery.

This calculator computes average velocity from past sprint data and uses it to forecast how many sprints are needed to complete remaining backlog items. It also provides a velocity range (min to max) for probabilistic planning, which is more realistic than single-number estimates.

Velocity stabilizes after 3–5 sprints for a consistent team. New teams, team composition changes, or major technology shifts will cause velocity to fluctuate. Using a rolling average of the last 3–6 sprints provides the most reliable forecast.

When This Page Helps

Velocity-based forecasting replaces wishful thinking with data. This calculator turns historical sprint data into actionable completion estimates, helping product owners and stakeholders set realistic expectations.

How to Use the Inputs

1. Enter the total story points completed across recent sprints.
2. Enter the number of sprints included in the calculation.
3. Enter the remaining story points in the backlog.
4. Review the average velocity and sprint forecast.
5. Use the range to communicate best-case and worst-case timelines.

Example Calculation

Tips & Best Practices

• Use a rolling average of 3–6 sprints for the most reliable velocity.
• Don't count story points from unfinished stories (the 'done' count only).
• Velocity naturally varies 15–25% sprint-to-sprint; this is normal.
• Don't compare velocity between different teams — story point scales differ.
• Factor in upcoming holidays, PTO, and team changes when forecasting.
• If velocity is declining, look for process issues, not individual performance.

Velocity as a Planning Tool

Velocity's primary purpose is forecasting, not performance measurement. It answers the question: at our current pace, when will we finish the remaining work? Used correctly, it sets realistic expectations and highlights when deadlines are at risk.

Velocity Ranges for Better Forecasting

Single-number forecasts create false precision. Using a velocity range (e.g., 28–42 points per sprint based on historical min/max) produces a timeline range that honestly communicates uncertainty. This is more useful for stakeholders than a single date.

Velocity Anti-Patterns

Avoid using velocity as a performance metric, comparing across teams, mandating velocity targets, or counting partial work. These practices distort the metric and destroy its value as a planning tool. Velocity should be owned by the team, not management.

Frequently Asked Questions

• How many sprints do I need for a reliable velocity?

  At least 3 sprints to see a pattern, and 5–6 sprints for a stable average. Fewer than 3 sprints gives unreliable data. Use the range (min to max) rather than the average for planning until you have enough history.

• Should I include the current sprint?

  No, only include completed sprints. The current sprint's velocity isn't known yet. Including partial data distorts the average. Update velocity metrics at the end of each sprint during retrospective.

• What if team size changes?

  Significant team changes (adding or losing members) invalidate historical velocity. After a change, allow 2–3 sprints for the new team to stabilize before using velocity for forecasting. In the interim, use per-person velocity as a rough guide.

• Can velocity be used to compare teams?

  No. Story point scales are team-specific. A team averaging 30 points isn't less productive than a team averaging 80 points. They simply calibrate points differently. Use velocity only for within-team forecasting.

• What causes velocity to decline?

  Common causes include increasing technical debt, scope creep within stories, team member departures, unclear requirements leading to rework, and growing operational burden (on-call, support). Investigate trends in retrospectives.

• Should I try to increase velocity?

  Not directly. Velocity is a planning tool, not a performance target. Pressuring teams to increase velocity leads to story point inflation, reduced quality, and unreliable estimates. Focus on removing impediments and improving flow.