Skip to main content

Scenario Planner

What-if modeling & allocation scenarios

Scrum Master Guide: Scenario Planning

The Scenario Planner lets you model resource allocation scenarios by adjusting variables like team size and project priorities to see how changes affect delivery capacity. Use it before quarter planning to prepare data-backed proposals, or mid-sprint to evaluate the impact of unexpected changes. The key question: “If we shift resources from X to Y, what does the delivery forecast look like?”

Current Allocation

Feature Development12.4 FTE
Keep the Lights On5.8 FTE
Tech Debt3.2 FTE
Growth / Scaling2.1 FTE
Unallocated1.5 FTE

Scenario: Shift 1.8 FTE from KTLO to Features

Feature Development14.2 FTE
+1.8 FTE
Keep the Lights On4 FTE
-1.8 FTE
Tech Debt3.2 FTE
Growth / Scaling2.1 FTE
Unallocated1.5 FTE

Delta Summary

  • Feature Development: +1.8 FTE(12.4 → 14.2)
  • Keep the Lights On: −1.8 FTE(5.8 → 4.0)
  • Net change: 0 FTE— rebalance, not growth

API Explorer

MockMock

Using Scenarios in Planning

  • Quarter Planning: Build 2–3 scenarios before the planning session. Present the tradeoffs clearly: “Scenario A adds 2 FTE to features but drops KTLO coverage to 16%. Scenario B keeps current balance but extends the roadmap by 3 weeks.”
  • Mid-Sprint Adjustment: When priorities shift unexpectedly, model the reallocation impact before committing. Moving engineers between categories mid-sprint has a context-switching cost that the raw FTE numbers don't show.
  • Stakeholder Communication: Scenarios turn allocation conversations from opinions into data. Instead of “we need more engineers,” present: “Shifting 1.8 FTE from KTLO to Features increases feature throughput by an estimated 15% but creates KTLO risk in areas X and Y.”