Capacity Planning

What is Capacity Planning?

Capacity planning is the process of estimating the people, skills and time an organization will have available and comparing them with demand from planned work, so commitments match what can realistically be delivered.

Updated November 2026 · 3 min read


Capacity planning is the process of comparing the work an organization wants to do with the time and skills its people actually have, so that it commits only to what it can deliver. It answers a question many organizations skip: do we have enough people with the right skills to do everything we have approved? Portfolios are often built by adding up the work leaders want, with little check against the time actually available. The result is overload. Teams spread across too many priorities, work queues behind a few specialists and delivery slows across the board. Capacity planning makes the constraint visible before commitments are made.

In portfolio management, it works at three levels. At the portfolio level, it compares total demand with total capacity to decide how much work can start. At the team or skill level, it shows which shortages will hold up delivery. Over longer horizons, it informs hiring, contracting and training.

How to calculate capacity

Capacity is the time people actually have for planned work. Start from total hours or full-time equivalents (FTEs), then subtract:

  • Holidays, leave and training.
  • Meetings, administration and other overhead.
  • Time spent running existing systems and services: support, maintenance, incidents and small enhancements.

The last item is the one most often left out. In many IT organizations, keeping existing systems running consumes half or more of total capacity. A plan that treats every engineer as fully available for new projects will fail before it starts.

Agile teams often measure capacity as throughput instead, such as the number of features a team typically completes in a quarter. The unit matters less than using the same one consistently.

Comparing capacity and demand

Demand comes from approved work, planned product work, maintenance and requests still waiting for approval. Each item is estimated by role or skill and time period, roughly at first and in more detail as it gets closer to starting. Comparing the two by skill and quarter shows three things:

  • Overall fit: whether total demand exceeds total capacity, which means some work must wait or be stopped.
  • Bottlenecks: skills where demand far exceeds supply even if the overall numbers balance, such as data engineers or security architects.
  • Slack: skills with spare capacity, which may be redeployed or reduced.

An example

Consider a hypothetical IT department of 200 people planning next year's portfolio. Leaders have shortlisted 48 projects. The PMO estimates that after leave, overhead and run work, about 110 FTEs are available for projects. The 48 projects need 160 FTEs. Looking by skill, the gap is worst for data engineers: demand is 28 FTEs and supply is 9. The leadership team cuts the list to 31 projects, delays four data-heavy projects to the second half of the year and approves hiring six data engineers. Without the capacity check, all 48 would have been approved and most would have run late.

Why full utilization is the wrong target

It is tempting to plan teams at 100% of their available time. Queueing theory shows why that backfires. As a resource approaches full utilization, small variations in work cause wait times to rise sharply, so work takes much longer to flow through. Most capacity plans leave a buffer, often 15% to 25%, for unplanned work, rework and urgent requests. See resource utilization.

Common pitfalls

  • Ignoring run work and overstating capacity for new projects.
  • Planning by headcount only, without looking at skills, which hides bottlenecks.
  • Planning once a year, so capacity plans fall out of date as demand changes.
  • Treating estimates as commitments, which encourages padding.

Capacity planning is closely related to resource planning, which forecasts specific resource needs, and resource management, which assigns people to work. It is an input to portfolio prioritization and demand management.

Frequently asked questions

What should be subtracted when calculating capacity for planned work?

Start from total hours or full-time equivalents, then remove holidays, leave and training, meetings and administration, and the time spent running existing systems, including support, maintenance, incidents and small improvements. Run work is the item most often forgotten, and in many IT organizations it takes half or more of total capacity.

How much buffer should a capacity plan leave?

Most capacity plans hold back a buffer, often 15% to 25%, for unplanned work, rework and urgent requests. Planning people at 100% of their available time backfires, because queueing theory shows that as utilization approaches full, small variations cause wait times to rise sharply and work takes much longer to flow through.

How is capacity planning different from resource planning?

Capacity planning compares total available time and skills with total demand to decide how much work the organization can commit to. Resource planning forecasts specific resource needs for that work, and resource management assigns people to it. Capacity planning comes first and feeds portfolio prioritization and demand management.

What does comparing capacity with demand reveal?

Comparing the two by skill and quarter shows overall fit, meaning whether total demand exceeds capacity so some work must wait or stop. It also exposes bottlenecks, skills such as data engineers where demand far exceeds supply even when totals balance, and slack, skills with spare capacity that could be redeployed or reduced.