Team Capacity Calculator

Team capacity estimates how much work an engineering team can realistically deliver during a sprint after accounting for operational overhead. Capacity is reduced by meetings, support work, leave, interruptions, context switching, and planning uncertainty. Actual delivery capacity is often substantially lower than total available hours.

Basic calculation: Gross Hours - Overhead - Interruptions - Leave - Planning Adjustment. Example: 8 engineers x 40 hours/week x 2 weeks = 640 gross hours. After operational overhead, committed capacity can drop to about 237.9 hours.

Engineering teams rarely spend 100% of time on project work. Time is frequently consumed by meetings, support, production incidents, onboarding, coordination, and context switching. More engineers can also increase communication overhead.

Meetings consume engineering time and directly affect delivery throughput. Examples include standups, sprint planning, architecture discussions, stakeholder meetings, and retrospectives. Ignoring meetings often leads to unrealistic sprint plans.

Many teams spend substantial time on incidents, bug fixes, customer escalations, maintenance, and operational support. These activities reduce project bandwidth.

Interruptions include unexpected work that pulls teams away from planned delivery. Examples include production outages, executive requests, urgent fixes, customer escalations, and dependency issues. High interruption rates often reduce predictability.

Switching between projects or priorities creates hidden costs, such as restarting mental context, reloading technical details, and multitasking inefficiency. Frequent switching often reduces throughput.

Teams frequently estimate optimistically. Confidence adjustment intentionally reduces raw capacity to create more reliable commitments. Example: raw capacity 264 hours with a 10% confidence reduction gives about 237.9 committed hours.

Effective FTE estimates productive staffing after accounting for capacity losses. Example: team size 8 can result in an effective FTE of about 2.97. This often reveals that a larger team may effectively behave like a much smaller delivery team.

Story point prediction converts available capacity into estimated delivery throughput. Formula: Predicted Story Points = Effective Capacity x Historical Velocity. Story point estimates are directional and should be validated against actual sprint performance.

Low utilization may indicate excessive operational overhead, staffing imbalance, process inefficiencies, or fragmented priorities. Understanding capacity loss patterns can improve planning quality.

No. Historical velocity is usually the strongest predictor of future delivery. Capacity planning should complement velocity history, sprint trends, team maturity, and operational context.

Useful follow-ups are Architecture Scorecard, Technical Due Diligence Risk Score Calculator, AI ROI Calculator, Contractor Rate Calculator, and ROI Calculator.