ForHosting KIT · Developer Utilities

Team sprint capacity calculator

Turn individual availability into a realistic sprint commitment before planning begins.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

Enter each team member's available hours, apply a shared focus factor, and receive the team's usable capacity in hours or story points. The calculation keeps raw availability separate from focused delivery time, so meetings, support, coordination, and other unavoidable work are acknowledged rather than hidden. A member-by-member breakdown makes the result easy to review with the team and straightforward to copy into a planning worksheet, sprint forecast, or capacity record.

Start with actual availability, not nominal workdays

A reliable sprint forecast begins with the hours people can genuinely contribute during the specific sprint. Do not multiply headcount by a standard workweek and stop there. For every team member, subtract holidays, leave, training, known appointments, on-call recovery time, and days assigned to another initiative before entering available hours. This produces a transparent baseline that can be discussed and corrected. The calculator totals those entries without assuming that every person has the same schedule. A part-time engineer, a designer shared with another group, and a full-time tester can therefore sit in one plan without awkward manual adjustments. Names act as labels in the breakdown and must be unique, which helps reviewers connect each contribution to the source schedule. Available hours may be zero when someone belongs to the team but cannot contribute to this sprint. Keep that person in the list if their zero availability is useful context; otherwise omit them. The resulting total available hours is the team's time budget before delivery overhead is considered.

Use the focus factor to represent delivery reality

The focus factor is the percentage of available time expected to become planned delivery capacity. A factor of 70 means that seventy percent of the entered availability is reserved for planned sprint work, while the remainder recognizes activities such as ceremonies, reviews, collaboration, support, communication, and routine interruptions. The calculator applies one factor consistently to every member and reports both the original hours and the focused hours, making the assumption visible. Choose the percentage from evidence when possible: compare completed planned work with actual availability across several representative sprints, then revisit it when the team's environment changes. A newly formed team, a release period, or a heavy support rotation may justify a different factor from a stable product cycle. The allowed range is zero through one hundred percent. Zero can model a sprint with no planned delivery capacity, and one hundred models the exceptional assumption that all available time is usable. Values outside that range are rejected instead of being silently clamped, because an unnoticed typo would create a misleading commitment.

Choose hours or convert the plan to story points

Select hours when the team plans directly against time or when you want the least interpretive result. The planned capacity is then simply total available hours multiplied by the focus-factor percentage. Select story points only when your team already uses a stable local relationship between focused hours and a planning point. In that mode, provide the number of focused hours represented by one story point; the calculator divides focused capacity by that value. This conversion is a planning convention, not a universal productivity measure, and it should never be used to compare teams. Story points reflect a team's own uncertainty, complexity, and working agreements, so reuse a ratio only within the context where it was established. The member breakdown shows each person's focused hours and capacity contribution, while the team result remains the primary figure for sprint planning. Fractional results are retained and rounded predictably to four decimal places. Teams may round the final commitment downward according to their own policy, but keeping the calculated value visible preserves the assumptions and avoids compounding hidden rounding across individual members.

Prepare sprint planning

Convert leave-adjusted schedules into one reviewable delivery-capacity figure before selecting backlog work.

Model staffing changes

Compare capacity when a shared specialist, new teammate, or support rotation changes the hours available to the sprint.

Document planning assumptions

Record availability, focus factor, conversion ratio, and member contributions alongside a sprint commitment.

What does the focus factor mean?

It is the percentage of available hours expected to support planned delivery after normal overhead and interruptions.

Can the focus factor be greater than 100 percent?

No. The accepted range is 0 through 100 percent, and values outside it return an invalid-input error.

How are story points calculated?

Focused team hours are divided by the supplied hours-per-story-point planning ratio. The default ratio is six hours per point.

Should story points be compared across teams?

No. The conversion is a local planning convention and does not make story points a standardized productivity measure.

What should available hours exclude?

Exclude known leave, holidays, training, other assignments, and any other time that is not available during the sprint.

What does an API calculation cost?

Each API request costs $0.002. The browser calculation is also available directly on this page.

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.

POSThttps://api.kit.forhosting.com/biz/team-capacity-planning

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.

curl -X POST https://api.kit.forhosting.com/biz/team-capacity-planning \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"team_members":[{"name":"Avery","available_hours":60},{"name":"Morgan","available_hours":48},{"name":"Riley","available_hours":72}],"focus_factor":70}'
{
  "team_members": [
    {
      "name": "Avery",
      "available_hours": 60
    },
    {
      "name": "Morgan",
      "available_hours": 48
    },
    {
      "name": "Riley",
      "available_hours": 72
    }
  ],
  "focus_factor": 70
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "biz.team_capacity_planning",
  "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.

Per request$0.002

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

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Read the full KIT documentation →