ForHosting KIT · Dates & time

Calculate agile team average velocity and planning velocity

Enter the completed story points of recent sprints to get your team's average velocity and a cautious planning figure: five sprints totalling 150 points average 30, with a suggestion of 26.594123 once the spread is subtracted. Free in your browser.

Free
Runs in your browser
No sign-up
Your data stays on your device

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

Worked example

If you enter

Sprints: 32, 28, 35, 30, 25

You get

Sprint count: 5
Total story points: 150
Average velocity: 30
Standard deviation: 3.405877

This agile velocity calculator turns a sequence of completed sprint story-point totals into a transparent planning baseline. It reports the team's average velocity, the population standard deviation across the supplied sprints, and a conservative suggestion equal to the average minus one standard deviation, never below zero. Use recent, comparable sprints to support capacity conversations without treating a forecast as a promise or allowing one unusually productive iteration to set the next commitment.

Choose sprint data that represents the team you are planning for

Start with completed story points from recent sprints run by substantially the same team under a reasonably consistent definition of done. Enter one total for every sprint, preferably in chronological order so the source is easy to review, although order does not change the calculation. Include work only when your team counted it as completed at the sprint boundary.

Do not add partially finished stories, planned points, or work transferred to another team. A longer history can smooth isolated surprises, but an old history may describe a different team, product, or delivery process. Five to ten comparable sprints is often a practical discussion window, yet the calculator intentionally accepts a single sprint when that is all you have; its standard deviation will then be zero.

If staffing, sprint length, estimation scale, or workflow changed materially, select only the observations that remain comparable or calculate separate periods. The result is strongest when the input answers one precise question: how many points has this current team recently finished per sprint under current working conditions?

Understand the average and conservative suggestion

The average velocity is the arithmetic mean: all completed story-point totals are added and divided by the number of sprints. The calculator then measures population standard deviation across exactly those supplied observations. A small standard deviation means the totals cluster near the average; a large value signals that recent delivery has varied more widely.

Suggested planning velocity is calculated as the average minus one population standard deviation and is floored at zero. This is a deliberately cautious baseline, not a probability guarantee, service-level commitment, or statistical confidence bound. Population deviation is used because the supplied window is treated as the complete planning history you selected, rather than as a sample requiring Bessel's correction.

Outputs are rounded to six decimal places for stable automation, while the calculation uses full numeric precision internally. Keep the unrounded conceptual distinction in mind: an average describes the center of past results, whereas the suggested value adds a buffer for observed variation. Teams may round the suggestion down to a whole point for a planning conversation, but should record that local choice separately.

Use velocity as evidence, not as a performance target

Bring the result into sprint planning alongside known availability, holidays, production support, dependencies, and the shape of the upcoming backlog. If the suggested velocity is 27.4 points, it can support a conversation around roughly 27 points, but it should not override information that the next sprint is unusual. Recalculate on a regular cadence with a consistent rolling window, and retain the input totals so anyone can reproduce the number.

A sudden change in standard deviation can be more informative than a small change in the mean because it invites the team to examine interruptions, oversized stories, estimation drift, or unstable scope. Avoid comparing velocity between teams: story points are a local relative scale, so two equal numbers do not imply equal output or effectiveness. Never use the conservative suggestion as an individual productivity quota or pressure the team to inflate estimates.

The useful outcome is a shared, inspectable forecast that makes uncertainty visible.

What you can do with it

Prepare for sprint planning

Turn the current team's recent completed totals into a cautious capacity baseline before discussing the next backlog.

Review delivery consistency

Compare average velocity with standard deviation to distinguish a stable pattern from highly variable sprint outcomes.

Automate a rolling forecast

Feed the latest sprint totals from an internal report into a deterministic calculation that is easy to reproduce and audit.

FAQ

Which standard deviation does the calculator use?

It uses population standard deviation across the exact sprint window supplied, dividing squared deviations by the number of observations.

Why subtract one standard deviation from the average?

It provides a simple conservative allowance for recent variation. It is a planning heuristic, not a guaranteed minimum or formal confidence interval.

Can the suggested planning velocity be negative?

No. The average-minus-deviation result is floored at zero because negative completed story points are not a meaningful planning capacity.

Should incomplete stories be included?

No. Supply only story points your team considered completed at each sprint boundary under its consistent definition of done.

How many sprints should I enter?

Five to ten comparable sprints from the same team is often a practical window. A single sprint is accepted when that is all you have, but its standard deviation will then be zero.

Related tools

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/date/velocity-average-calculate

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/date/velocity-average-calculate \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"sprints":[32,28,35,30,25]}'

const res = await fetch("https://api.kit.forhosting.com/date/velocity-average-calculate", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "sprints": [
      32,
      28,
      35,
      30,
      25
    ]
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/date/velocity-average-calculate",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "sprints": [
        32,
        28,
        35,
        30,
        25
    ]
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/date/velocity-average-calculate", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"sprints":[32,28,35,30,25]}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"sprints":[32,28,35,30,25]}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/date/velocity-average-calculate", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "sprints": [
    32,
    28,
    35,
    30,
    25
  ]
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "date.velocity_average_calculate",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

Limits

`max_sprints`	1000
`max_story_points`	1000000

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.

Technical notes

Use velocity as evidence, not as a performance target

API automation costs $0.002 per request, while the deterministic calculation makes repeated checks straightforward and reproducible without hidden data sources.

Technical questions

What happens when no sprint data is provided?

The request returns an invalid_input error because an average cannot be calculated without at least one completed sprint value.

How much does an API calculation cost?

Each API request costs $0.002. The calculation is deterministic and does not contact external services.

Read the full KIT documentation →

Run — free

Worked example

Choose sprint data that represents the team you are planning for

Understand the average and conservative suggestion

Use velocity as evidence, not as a performance target

What you can do with it

Prepare for sprint planning

Review delivery consistency

Automate a rolling forecast

FAQ

Related tools

For developers — API access

API endpoint

Call it from your stack

Example request

Example response

Pricing

Limits

Errors

Technical notes

Use velocity as evidence, not as a performance target

Technical questions

thank you