Definition
Capacity Planning
Capacity planning is the practice of matching a team's committed work to the effort it can realistically deliver in a given period. It accounts for headcount, availability, holidays, meetings, and support load — not just an idealized full-time team. Planning to real capacity, rather than maximum capacity, keeps commitments achievable and prevents chronic over-loading of a sprint.
Key takeaways
- Capacity planning is the practice of matching a team's committed work to the effort it can realistically deliver in a given period. It accounts for headcount, availability, holidays, meetings, and support load — not just an idealized full-time team. Planning to real capacity, rather than maximum capacity, keeps commitments achievable and prevents chronic over-loading of a sprint.
- Capacity planning answers a deceptively simple question: how much can we actually take on?
- Planoda surfaces a team's historical velocity and throughput from completion events, giving planners an evidence-based ceiling instead of an optimistic guess when they decide how much to commit.
Capacity planning answers a deceptively simple question: how much can we actually take on? The naive answer multiplies people by hours, but real capacity is always lower. Someone is on vacation, a holiday eats two days, recurring meetings consume a slice of every week, and a portion of the team is always pulled into unplanned support or interruptions.
Doing it well means subtracting those realities before committing. A team that plans to 100% theoretical capacity is planning to fail, because the first interruption blows the plan. Mature teams plan to a deliberately lower number — leaving slack for the unexpected — and use their own historical velocity as the most honest input, since past throughput already bakes in the meetings and interruptions that estimates ignore.
Capacity planning operates at two scales. Inside a sprint it caps how much work to pull in. Across a roadmap it sanity-checks whether ambitions fit the team that exists, which is where over-commitment quietly originates — at the planning level, long before any single sprint.
Planoda surfaces a team's historical velocity and throughput from completion events, giving planners an evidence-based ceiling instead of an optimistic guess when they decide how much to commit.
Related terms
- VelocityVelocity is the average amount of work a team completes per cycle, measured in issues or story points. By tracking it over several cycles, teams forecast how much they can realistically take on next. Velocity is a planning aid for a specific team over time — never a target to maximize or a way to compare teams against each other.
- ThroughputThroughput is the number of work items a team completes in a given period — issues finished per week, for example. It is the simplest flow metric: a direct count of output over time. Tracked across periods, throughput reveals a team's real delivery capacity and is the basis for probabilistic, estimate-free forecasting.
- Sprint PlanningSprint planning is the meeting that opens a sprint, where the team reviews the prioritized backlog and decides what it will commit to in the coming iteration. The team agrees on a sprint goal, pulls a realistic amount of work it believes it can finish, and clarifies scope. The output is a concrete, achievable plan for the time-box ahead.
- Little's LawLittle's Law is a foundational result from queueing theory stating that, on average, the number of items in a system equals the rate items arrive (or complete) multiplied by the average time each spends in the system. For teams: average work in progress equals throughput times cycle time — which is why limiting WIP directly shortens cycle time.
- Monte Carlo ForecastingMonte Carlo forecasting predicts delivery by running thousands of simulated futures from a team's historical throughput, producing a probability rather than a single date. Instead of 'we'll finish on the 20th,' it answers 'an 85% chance of finishing by the 24th.' It replaces false-precision estimates with honest, evidence-based ranges drawn from how the team actually performs.