3-5 is the common rolling window. Less than 3 = noisy. More than 5 = stale (the team’s context has changed).

Should velocity ever go up?

Yes, modestly, as the team matures and removes friction. A 50% jump in one sprint is a red flag — either you padded the estimates or you’re measuring the wrong thing.

Is velocity a productivity metric?

Inside the team: yes. Across teams: NO. Never compare velocities between teams — story-point scales are not normalised.

Task Hub

Sprint Velocity Calculator

Average + trend + capacity-adjusted forecast

Calculate scrum team velocity, see the trend, and forecast next sprint based on capacity.

Start 14-day free trial See how it works → Task Hub

Loading tool...

Save hours every week

Calculate one sprint’s velocity — or get auto-tracked velocity across every sprint with capacity forecasting in Task Hub.

Start 14-day free trial

Scrum teams use velocity to commit honestly to upcoming sprint work. This Sprint Velocity Calculator takes your last three sprints’ velocity, computes the rolling average, flags trend direction (up / down / stable), and forecasts next sprint adjusted for team capacity — because if a person is on holiday, committing the same velocity is dishonest. Also tells you how many sprints it will take to finish 50 points at the current rate, so you can sanity-check release plans. Use it in sprint planning.

How to Use

1 Enter velocity from last 3 sprints 2. Enter the team capacity for the next sprint (100 = full, 80 = one person out, etc.) 3. Read the average, the trend and the forecast

Benefits

Rolling 3-sprint average

Trend signal (up / down / stable)

Capacity-adjusted forecast

Sprints-to-target estimate

FAQ