Capacity Planning

Estimating the amount of work a team can realistically complete during a single iteration or program increment.

Key Points

  • Uses team availability, skills, holidays, and existing commitments to forecast workable load.
  • Informs iteration/PI scope so the team neither overcommits nor sits idle.
  • Often expressed in story points, ideal hours, or average throughput based on historical data.
  • Recalibrated each planning cycle to reflect changes in WIP, dependencies, and risks.

Example

Before PI planning, a team totals 60 person-days for the next iteration after accounting for vacations and support duties. Their recent average throughput is about 25 story points per iteration. They set a target of 24-26 story points, reserve a small buffer for unplanned work, and select backlog items to match that capacity.

PMP Example Question

During iteration planning, a Scrum team reviews member availability, recent velocity, and known support work to set a realistic commitment. What practice are they applying?

  1. Release burnup tracking
  2. Definition of Done
  3. Capacity planning
  4. Earned value analysis

Correct Answer: C — Capacity planning

Explanation: Capacity planning determines how much work the team can take on in the upcoming iteration or program increment based on availability and historical performance.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Seven sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Advance your Lean Six Sigma expertise!

HK School of Management helps you take Lean Six Sigma to the next level without the overwhelm. Master advanced statistical tools, Excel-based analysis, and real-world improvement techniques to solve complex problems with confidence. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More