How many sprints should I use to calculate velocity?

Use the last 3–6 sprints for the most accurate average. Fewer than 3 sprints produces unreliable data. Discard outlier sprints (holiday weeks, sprints with team member changes) or include them to reflect real-world variability.

What is a good sprint velocity?

There is no universal "good" velocity — it depends on team size, sprint length, and story point scale. What matters is consistency and trend. A team with stable velocity of 30 points per 2-week sprint is more predictable than one varying between 20 and 50.

How do I improve sprint velocity?

Improve through: better sprint planning (realistic commitment), reducing mid-sprint interruptions, clearing blockers quickly, investing in automation and CI/CD, and reducing technical debt that slows feature development.

Can I compare velocity across teams?

No. Story points are relative to each team's own scale. Comparing velocity across teams is meaningless — a team that inflates story point estimates will have higher velocity but complete no more work. Velocity is only meaningful within the same team over time.

How do story points relate to hours?

They don't — directly. Story points measure relative complexity, not time. A 3-point story might take 2 hours or 2 days depending on who works on it. Teams should resist converting points to hours; instead use velocity (points/sprint) to forecast sprint count and derive calendar dates.

Is my data sent to a server?

No. All velocity calculations run locally in your browser. Sprint history, backlog size, and team capacity inputs are never transmitted to any server or stored anywhere.

How is sprint velocity calculated?

Add up the story points completed in each of the last few sprints and divide by the number of sprints. Three to six sprints is a good sample. Only count work that was fully completed — partially done items do not contribute to velocity.

How do I forecast a backlog with velocity?

Divide the remaining backlog points by the average velocity to get the number of sprints needed. Using the highest and lowest recent velocity gives an optimistic and pessimistic range, which is more honest than a single number.

saas

Free Sprint Velocity Calculator — Agile Team Velocity & Backlog Forecast

Sprint velocity is the average number of story points (or tasks) a team completes per sprint. Calculated from historical sprint data, velocity is used to forecast how many sprints remain to complete the backlog, helping product managers plan releases and manage stakeholder expectations.

Free — No SignupRuns in BrowserData Never Uploaded

saas

Calculate average sprint velocity from historical sprints and project remaining backlog.

Average sprint velocity from past sprints
Backlog forecast in sprints and weeks
Optimistic and pessimistic completion range
Projected completion date
Velocity trend chart
Client-side only — nothing is uploaded

Features

Everything you need in one Sprint Velocity Calculator

Average sprint velocity

Averages story points across your recent sprints — the single number agile teams use to plan future capacity.

Backlog forecast

Divides the remaining backlog by velocity to project how many sprints and calendar weeks the work will take.

Optimistic / pessimistic range

Uses your best and worst recent sprints to give a forecast range — far more honest than a single date.

Velocity trend chart

A bar chart of past sprints with the average line shows whether the team is speeding up, steady, or slowing.

How It Works

How to use Sprint Velocity Calculator

Enter past sprint data

Input story points completed for each of your last 3–6 sprints.

Enter remaining backlog

Add the total story points in your current product backlog.

See forecast

The calculator shows average velocity, sprints remaining, and estimated completion date.

Format Comparison

Velocity inputs explained

Input	What it does
Points per sprint	The completed work per sprint that builds the average
Average velocity	Mean points per sprint — the planning number
Min / max velocity	Recent best and worst — defines the forecast range
Backlog points	Total work remaining to be delivered
Sprints remaining	Backlog divided by velocity, rounded up

Troubleshooting

How to fix common syntax errors

Most “invalid JSON” failures come from a small set of mistakes. Paste the failing JSON above, click Validate, and the tool points you at the exact line and column.

Including incomplete stories in velocitySprint ends — 3 half-done stories counted as partial points

Only count stories fully done (accepted by PO, meets DoD). Partial credit inflates velocity and makes forecasts optimistic.

Not adjusting velocity when team composition changesNew developer joins — 3-sprint average includes old team composition

Reset velocity baseline when team size changes by more than one person. Old velocity with different headcount is not a reliable predictor.

Using spike or research sprints in velocity averageSprint 4 was an architecture investigation spike — included in average

Spikes and research sprints have no deliverable story points. Exclude them from velocity calculation entirely.

Treating velocity as a performance targetManager tells team "velocity must be 40 points next sprint"

Setting velocity targets causes point inflation — teams estimate higher to "hit" the number. Use velocity as a forecasting input, not a performance metric.

Not adjusting for planned leave and holidaysChristmas sprint with half the team away — same velocity expected

Reduce capacity proportionally for sprints with planned absence. A 2-person team losing one member for a week runs at 75% capacity, not 100%.

Comparing velocity across teamsTeam A (velocity 40) vs Team B (velocity 25) — concluding A is faster

Story point scales are relative to each team. Team B may estimate conservatively and deliver more real value. Velocity is team-internal, never cross-team.

FAQ

Frequently asked questions

Sprint velocity is the average number of story points a team completes per sprint, calculated over the last 3–6 sprints. It is used for forecasting: remaining backlog / average velocity = sprints to completion.

Related Tools

You might also need

Project Timeline Estimator

Estimate software project timeline in sprints from a feature checklist and team size.

MVP Cost Estimator

Estimate the cost to build a software MVP based on features and team type.

Build vs Buy Calculator

Compare the 5-year cost of building custom software vs buying a SaaS subscription.

Custom Software ROI Calculator

Calculate payback period and 5-year ROI for a custom software investment.

Tech Stack Recommender

Answer 5 questions about your project and get a recommended technology stack.

SaaS Pricing Calculator

Model SaaS pricing tiers and forecast MRR from customer distribution across plans.

Meeting Cost Calculator

Calculate the true cost of a meeting based on attendees, duration, and average salary.

Cold Email ROI Calculator

Calculate projected revenue from a cold email campaign using open, reply, and close rates.

References

Need this built into your product?

We design and build custom software — SaaS platforms, MVPs, AI agents, and web apps.

Let's talk

Custom SaaS Development

End-to-end SaaS — from schema design to production deployment.

MVP Development

Working product in 6–8 weeks. Fixed price, committed timeline.

AI Agents for SaaS

AI-powered automation for support, onboarding, and revenue ops.

Web App Development

Full-stack web apps with modern architecture and cloud deployment.

Have a project in mind?

We turn ideas into production-ready software — SaaS, web apps, mobile, and AI agents. Fixed price. Committed timeline. No surprises.