# Sprint capacity calculator: team hours, story points and delivery date

> Sprint capacity is the focused working time a team has in a sprint: people × working days, minus leave and holidays, × focus hours per day, minus time for scrum ceremonies and meetings. To plan story points, scale your average velocity by available capacity compared with a full sprint. Dividing the remaining backlog by that velocity gives the number of sprints, and so a delivery date.

- Interactive version: https://infikeytechnologies.com/tools/sprint-capacity-calculator
- Type: free instant calculator
- Category: Team & outsourcing
- Last reviewed: 2026-10-05
- Publisher: Infikey Technologies (https://infikeytechnologies.com)

## Example result (default inputs)

| Input | Value |
| --- | --- |
| Developers in the team | 5 |
| Working days per sprint | 10 |
| Leave & holidays this sprint (person-days, whole team) | 3 |
| Focus hours per person per day | 6 |
| Time in meetings & ceremonies | 12% |
| Average velocity (points per full sprint) | 40 |
| Remaining backlog (story points) | 300 |

**Story points to plan this sprint: 38.** This sprint the team has about 248 focus hours and capacity for about 38 story points. The 300-point backlog needs about 8 sprints (16 weeks).

94% of normal capacity is available — plan about 38 story points this sprint.

| Metric | Value |
| --- | --- |
| Focus hours available | 248 hours |
| Person-days available | 47 of 50 |
| Capacity vs a full sprint | 94% |
| Sprints to finish the backlog | 8 |
| Weeks to finish the backlog | 16 |

### Backlog burn-down by sprint

| Item | Value | Detail |
| --- | --- | --- |
| Now | 300 pts |  |
| After sprint 1 | 262 pts |  |
| After sprint 2 | 222 pts |  |
| After sprint 3 | 182 pts |  |
| After sprint 4 | 142 pts |  |
| After sprint 5 | 102 pts |  |
| After sprint 6 | 62 pts |  |
| After sprint 7 | 22 pts |  |
| After sprint 8 (selected) | 0 pts |  |

- Later sprints assume full capacity at your average velocity. Add a buffer of 10–20% for unplanned work and new scope.

Open this result on the website: https://infikeytechnologies.com/tools/sprint-capacity-calculator?members=5&sprint_days=10&days_off=3&focus_hours=6&ceremonies=12&velocity=40&backlog=300

## Use from a link or API

Add these query parameters to https://infikeytechnologies.com/tools/sprint-capacity-calculator (pre-filled page), https://infikeytechnologies.com/tools/sprint-capacity-calculator.md (this plain-text page) or https://infikeytechnologies.com/api/tools/sprint-capacity-calculator (JSON).

| Parameter | Meaning | Accepted values |
| --- | --- | --- |
| `members` | Developers in the team | number from 1 to 50, default 5 |
| `sprint_days` | Working days per sprint | number from 1 to 30, default 10 |
| `days_off` | Leave & holidays this sprint (person-days, whole team) | number from 0 to 500, default 3 |
| `focus_hours` | Focus hours per person per day | number from 1 to 12, default 6 |
| `ceremonies` | Time in meetings & ceremonies | number from 0 to 60 (%), default 12 |
| `velocity` | Average velocity (points per full sprint) | number from 1 to 2000, default 40 |
| `backlog` | Remaining backlog (story points) | number from 0 to 100000, default 300 |

- Two-week sprint, small team: https://infikeytechnologies.com/tools/sprint-capacity-calculator?members=4&sprint_days=10&days_off=2&focus_hours=6&ceremonies=12&velocity=30&backlog=180
- Holiday sprint: https://infikeytechnologies.com/tools/sprint-capacity-calculator?members=6&sprint_days=10&days_off=15&focus_hours=6&ceremonies=12&velocity=48&backlog=400
- One-week sprints: https://infikeytechnologies.com/tools/sprint-capacity-calculator?members=5&sprint_days=5&days_off=0&focus_hours=6&ceremonies=12&velocity=20&backlog=120

## How it is calculated

- **Available person-days**: developers × sprint days − leave & holidays
- **Focus hours**: available person-days × focus hours per day × (1 − meetings %)
- **Points this sprint**: average velocity × available person-days ÷ full person-days
- **Sprints to finish**: remaining backlog ÷ average velocity, rounded up

## Capacity vs velocity

Capacity is time: how many focused hours the team has this sprint. Velocity is output: how many story points the team usually completes in a sprint.

Velocity already reflects your team’s normal meetings, reviews and interruptions, so the most reliable plan scales average velocity by this sprint’s availability, rather than converting hours directly into points.

## Sprint planning checklist

1. Collect leave, public holidays and on-call duties for everyone.
2. Calculate available capacity and the matching story points.
3. Pull the highest-priority refined stories up to that number.
4. Leave a buffer for bugs and support work.
5. Agree a sprint goal that is still met if one story slips.

## Why velocity changes

- Team members joining or leaving.
- Holidays, illness and on-call duties.
- Unclear or unrefined stories that grow during the sprint.
- Technical debt slowing down every change.
- Re-estimating points in different ways from sprint to sprint.

## FAQ

### How do you calculate sprint capacity?

Multiply the number of developers by the working days in the sprint, subtract leave and holidays, multiply by focus hours per day, then remove the share of time spent in meetings and ceremonies.

### How do you calculate velocity in scrum?

Velocity is the total story points of work completed in a sprint. Use the average of the last three to five sprints for planning.

### How many hours a day is a developer productive?

Teams commonly plan five to six focused hours per person per day, because email, reviews and interruptions take the rest.

### How do I estimate a delivery date from story points?

Divide the remaining backlog by average velocity to get the number of sprints, then multiply by sprint length. Add a buffer for new scope.

### Should story points be converted into hours?

Generally no. Points measure relative size; capacity in hours is used to adjust how many points the team commits to in a particular sprint.

## Get expert help

Send these results to an Infikey Technologies specialist from the form on https://infikeytechnologies.com/tools/sprint-capacity-calculator#estimate or via https://infikeytechnologies.com/contact.

More free calculators: https://infikeytechnologies.com/tools.md

## Disclaimer

This calculator is provided free for general information and planning only. Results are estimates based on the inputs you enter and the assumptions described on this page, reference data such as published prices may change, and actual costs and outcomes will differ. Nothing on this page is financial, legal, tax, investment or other professional advice. Infikey Technologies Private Limited, Infikey Technologies LLC and their directors, employees and affiliates make no warranty, express or implied, about the accuracy, completeness or suitability of this tool or its results, and accept no liability for any loss or damage, direct or indirect, arising from its use or from reliance on its results. Verify all figures independently and seek professional advice before making any decision. Use of this tool is at your own risk.