Team Capacity

Capacity planning prevents over-commitment. QA leads use it to size exploratory testing, automation, and regression load against real availability.

Available hours = gross calendar hours − PTO − meetings/overhead.

Tip: Keep “People” and “Working Days” on the same basis (units, period, and definition) before you calculate.

Cluster: Software Testing hub · Professional KPIs · Percentage guide

Team capacity estimates focus hours available in a sprint after PTO and recurring meetings.

Enter headcount, working days, hours per day, PTO hours, and meeting/overhead hours.

Team members included in the capacity pool
Sprint or period working days
hrs
Productive hours per person per day
hrs
Total leave hours in the period
hrs
Ceremonies, training, and other non-focus hours

Available Capacity (hours)

Understanding Team Capacity

How we calculate. Available hours = gross calendar hours − PTO − meetings/overhead. See our methodology and accuracy policy .

Real-world scenario: A typical Team Capacity case uses people 5 and working days 10. Enter the same figures below to reproduce the worked path.

What is Team Capacity?

Capacity planning prevents over-commitment. QA leads use it to size exploratory testing, automation, and regression load against real availability.

  • Gross hours = people × working days × focus hours/day
  • Subtract PTO and ceremonies before committing work
  • 100% utilization is unsafe — leave slack for interrupts

The Formula

Team Capacity
Capacity = (People × Days × Hours/day) − PTO hours − Meeting hours

Worked Example

Scenario: 5 people, 10 days, 6 focus hours/day. PTO = 16 hours. Meetings = 40 hours.
Step 1: Gross = 5 × 10 × 6 = 300
Step 2: Subtract PTO 16 and meetings 40
Step 3: Capacity = 300 − 16 − 40 = 244 hours
Answer: Available capacity is 244 hours.

Common Use Cases

  • Sprint planning: cap commitment to available hours
  • QA staffing: see if regression fits the sprint
  • Holiday sprints: recompute when PTO spikes

Pro Tips

  • Use focus hours (e.g. 5–6), not raw 8-hour days
  • Include on-call drain in overhead when it is predictable
  • Split roles (dev vs QA capacity) for clearer plans
ScenarioWhen to use
Percent of a numberFinding a part of a whole (tax, tip, score)
Percent changeComparing old vs new values

Limitations: Team Capacity results are planning aids for Agile/QA teams—not contractual delivery commitments. Confirm definitions with your scrum/quality playbook.

Common mistakes

  • Swapping part and whole: The denominator must be the full total, not a subset.
  • Rounding too early: Carry extra decimal places through multi-step work before rounding the final percent.
  • Mixing percent and decimal forms: Enter rates in the format the calculator labels expect.

The worked example for team capacity was verified with the calculator form on this page—enter the same values to confirm the result.

When to use this calculator

  • Use this page when your wording matches team capacity and the form labels on screen.
  • Use percent of a number for “what is X% of Y?” problems.
  • Use number is what percent when you know part and whole and need the percent.

Still unsure about team capacity? Start with the quick answer above, then open the linked calculator that matches your wording.

Frequently Asked Questions

How do I use this team capacity calculator?

For team capacity, enter the values labeled on the form, then press Calculate. Compare the result to the worked example on this page.

What formula does this page use?

See the quick answer and formula box above for team capacity—the same percentage calculator expression is applied to your inputs.

What if my result looks wrong?

When checking team capacity, re-check part vs whole (or rate vs base), rounding, and whether percents were entered as 25 rather than 0.25 when the form expects percents.

Authoritative References

For Agile and software testing practices, consult: