Skip to content

πŸ‘₯ Team Capacity Planning ​

Matching available capacity to project demands.

Capacity calculation ​

Available capacity = Team size Γ— Working days Γ— Focus factor
  • Focus factor: typically 60-80% (accounts for meetings, support, admin)
  • Working days: subtract holidays, PTO, company events

Capacity planning steps ​

  1. Inventory resources β€” Who is available? Part-time or full-time?
  2. Map commitments β€” Existing projects, support rotations, on-call
  3. Calculate available capacity β€” Hours/points available per sprint
  4. Match to demand β€” Compare backlog needs vs capacity
  5. Adjust β€” Reprioritize, defer, or hire if gap is too large

Common capacity drains ​

DrainTypical impactMitigation
Meetings20-30% of timeAudit and reduce
Context switching15-25% lossBatch similar work
Support / on-call10-20% of teamRotate, shield dev time
Technical debtVariableAllocate 15-20% per sprint
Unplanned work10-20%Buffer in sprint capacity

Signs of overcommitment ​

  • Consistently missing sprint goals
  • Rising burnout or turnover
  • Quality dropping (more bugs, less testing)
  • Everything is "urgent"
  • No time for learning or improvement

Best practices ​

  • Plan at 70-80% capacity, never 100%
  • Track velocity trends, not just single sprints
  • Protect maker time (blocks of uninterrupted focus)
  • Make trade-offs visible to stakeholders

Pergame Knowledge Base