Resource Capacity Planning Calculator
Calculate the total available working hours for a team over a sprint or planning period, adjusting for availability and a planning buffer. Use it before sprint planning or project kickoff to set realistic commitments.
About this calculator
Resource capacity planning translates headcount into usable hours so teams can make commitments they can actually keep. The formula is: Capacity = teamSize × hoursPerDay × workingDays × availabilityFactor × (1 − bufferPercentage / 100). Team Size is the number of contributors; Hours per Day and Working Days define the raw calendar window. The Availability Factor (a decimal between 0 and 1) discounts for planned leave, training, and non-project meetings — a value of 0.8 means each person is 80% available for project work. The Planning Buffer (as a percentage) reserves additional capacity for unplanned work, bug fixes, or estimation error. Multiplying these factors together gives the net committable hours, which can then be compared against the estimated effort in the sprint backlog to determine whether the scope is achievable or needs to be trimmed.
How to use
Your team has 6 people working 8 hours/day over a 10-day sprint. Availability Factor is 0.85 (accounting for meetings and leave) and Planning Buffer is 15%. Step 1 — raw capacity: 6 × 8 × 10 = 480 hours. Step 2 — apply availability: 480 × 0.85 = 408 hours. Step 3 — apply buffer: 408 × (1 − 15/100) = 408 × 0.85 = 346.8 hours. Round down to 346 committable hours. If your sprint backlog estimates total 400 hours, you have a capacity gap of ~54 hours and should remove scope before the sprint starts.
Frequently asked questions
What is a realistic availability factor for a software development team?
Most software teams operate at an availability factor between 0.7 and 0.85 when accounting for recurring meetings (standups, retrospectives, planning sessions), ad-hoc requests, and occasional leave. A factor of 1.0 would imply every team member spends 100% of the workday on planned project tasks, which is unrealistic. Research and practitioner surveys suggest that knowledge workers spend 60–75% of their time on their primary project role. Start with 0.75 as a conservative baseline and adjust upward if your team has unusually disciplined calendar hygiene, or downward during high-ceremony periods like quarterly planning.
How much planning buffer should I include in a sprint capacity plan?
A planning buffer of 10–20% is common in agile teams and accounts for unplanned work such as production incidents, urgent bug fixes, and estimation inaccuracies. Newer teams or teams supporting live production systems should use 20% or higher because their unplanned work rate is harder to predict. Mature teams with stable products and good historical data can operate with a 10% buffer. The buffer is distinct from the availability factor — availability covers known, predictable time losses, while the buffer absorbs genuinely unknown demand. Both should be calibrated against actual sprint retrospective data over time.
How is resource capacity planning different from resource allocation?
Capacity planning determines how many hours a team can realistically deliver in a given period — it is the supply side of the equation. Resource allocation is the act of assigning specific tasks or workstreams to specific individuals to meet a demand. You must complete capacity planning before allocation, because committing to a sprint or project without knowing available capacity leads to overloading team members and missing deadlines. In practice, capacity planning sets the ceiling, and allocation decisions determine how that ceiling is distributed across competing priorities, roles, or parallel workstreams.