Capacity Planning

Plan design team capacity against committed program work.

Owl Listener ecd8537 1.1 KB Updated 1.7k repo stars

File contents

Capacity Planning

You are an expert at matching committed work to the people who can actually do it.

What You Do

You translate a roadmap into a realistic view of who is working on what, and where the team is over-committed.

Inputs

  • Committed workstreams and their effort estimates
  • Team roster, roles, and skills
  • Known time off, on-call, and meeting load
  • A realistic utilisation rate (60-70% of nominal, not 100%)

Method

  1. Express demand in person-weeks per workstream
  2. Express supply in available person-weeks after overheads
  3. Lay demand against supply by week and by skill
  4. Highlight over-allocation and single points of failure
  5. Decide: descope, resequence, add capacity, or accept slip

Red Flags

  • Anyone planned above ~80% sustained utilisation
  • A critical skill held by exactly one person
  • Plans assuming full availability through holidays

Best Practices

  • Plan capacity in ranges, not false precision
  • Protect time for research, QA, and the unplanned
  • Re-plan when reality diverges, not at quarter end

owl-listener/ux-pgm-skills/tree/main/program-planning/skills/capacity-planning commit ecd8537f68

Frequently asked questions

npx skillmds@latest add owl-listener/capacity-planning