How this calculator works
| Metric | Formula |
|---|---|
| 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 |
Worked example
With these inputs:
- 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).
| 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 |
Open this example in the calculator
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
- Collect leave, public holidays and on-call duties for everyone.
- Calculate available capacity and the matching story points.
- Pull the highest-priority refined stories up to that number.
- Leave a buffer for bugs and support work.
- 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.
Open this calculator with your numbers
Every option can be set in the web address, so you can bookmark a scenario or send it to a colleague. AI assistants such as ChatGPT, Gemini, Claude and Perplexity can use the same parameters to open this calculator with your numbers and the result already on the page.
| Parameter | What it sets | 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 |
Also available as plain text for AI assistants and a free JSON API (OpenAPI spec).
Last reviewed by the Infikey Technologies team.
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.