18 Team Capacity Planning

Team Capacity Planning is the practice of estimating how much work an agile team can realistically complete within a given iteration or planning horizon, based on the team's demonstrated historical throughput, available working time, and known constraints, so that commitments made during planning remain achievable rather than aspirational.

Why Capacity Planning Is Necessary

Preventing overcommitment

Teams that plan work based on optimism or external pressure rather than actual demonstrated capacity routinely commit to more than they can deliver, producing a persistent pattern of missed commitments, rushed work near the end of an iteration, and accumulating technical debt as shortcuts are taken to meet unrealistic targets.

Enabling reliable forecasting

Because stakeholders and dependent teams often need to plan around a team's expected output, capacity planning provides the basis for credible forecasts of what will be delivered and when, replacing guesswork with a repeatable estimation process grounded in the team's own historical performance.

Measuring Capacity

Velocity as a capacity indicator

Many agile teams track velocity, the amount of estimated work (commonly measured in story points) completed during past iterations, and use an average or range of recent velocities as the primary input for estimating how much new work can be taken on in an upcoming iteration.

Here V₁ through V₃ represent velocity from the three most recent iterations, illustrating a simple rolling-average approach to estimating a team's likely capacity for the next planning period.

Accounting for available time directly

Alternatively, particularly for newly formed teams without sufficient velocity history, capacity can be estimated more directly by totaling each team member's available working hours or days for the iteration, then adjusting for planned absences, meetings, and other non-project commitments to arrive at a realistic estimate of hours available for actual delivery work.

Adjustments to Raw Capacity Figures

Accounting for planned absences

Vacations, holidays, training, and known partial availability of team members must be subtracted from a naive full-time calculation, since capacity planning based on theoretical maximum availability rather than realistically expected availability will systematically overestimate what a team can deliver.

Accounting for non-development overhead

Time spent on activities outside direct delivery work, such as production support, cross-team collaboration, meetings, and administrative tasks, reduces the time genuinely available for planned iteration work and should be factored into capacity estimates based on the team's observed historical split between delivery and overhead work.

Accounting for new team formation and ramp-up

Newly formed teams, or teams that have recently changed composition, typically require an adjustment period during which their effective capacity is lower than their theoretical maximum, reflecting time needed to establish working norms, build familiarity with the codebase or domain, and develop effective collaboration patterns.

Capacity Planning Across Multiple Iterations

Capacity for release and long-term forecasting

Beyond single-iteration planning, teams and organizations use accumulated capacity data across multiple past iterations to forecast delivery timelines for larger bodies of work spanning several iterations or an entire release, translating iteration-level capacity into longer-range planning confidence.

Adjusting for planned capacity changes

When team composition is expected to change, such as through planned hiring, departures, or temporary reassignment, capacity forecasts must be adjusted accordingly rather than assuming that past velocity will continue unchanged into future periods where the underlying team capacity itself is shifting.

Why Team Capacity Planning Matters

Grounding commitments in reality

By basing planned work on a team's demonstrated and realistically adjusted capacity rather than idealized assumptions, capacity planning helps ensure that iteration commitments are both achievable and sustainable, protecting against the burnout and quality erosion that result from chronic overcommitment.

Supporting trust between teams and stakeholders

Consistent, capacity-grounded planning builds a track record of teams meeting their commitments, which in turn supports more effective coordination with other teams and more accurate expectations among stakeholders who depend on predictable delivery timelines.