What is Probabilistic Forecasting?

ISExample
Expressing forecasts as ranges with probabilities“There’s an 85% chance we complete 20–25 items”
Quantifying uncertainty explicitlyMakes risk visible
Using historical data to simulate outcomesMonte Carlo, throughput-based forecasting
Providing multiple confidence levels50%, 85%, 95%
Enabling risk-aware decision-makingTradeoffs based on likelihood
Treating forecasts as distributions, not pointsSpread, not single value
Communicating likelihood, not certaintyLanguage of probability
Updating forecasts as new data arrivesDynamic, adaptive
Separating commitment from predictionForecast ≠ promise
Making variability part of the modelNot noise—signal

What is Not Probabilistic Forecasting?

IS NOTExample
Single-point estimation“We will deliver 23 items”
Deterministic forecastingAssumes one outcome
Commitment-based planningTreating estimates as guarantees
Averaging without variability“We usually do ~20”
Best-case / worst-case guessingNot grounded in data
False precisionExact numbers without confidence
Ignoring historical dataGut feel only
Binary thinkingDone / not done
Static forecastsNot updated with new info
Hiding uncertaintyRisk is implicit or invisible
Velocity-as-truthTreating velocity as fixed capacity
Date-driven certaintyBack-solving to meet a date

What Are Some Examples of Probabilistic Forecasting?

  • We can complete [some number] PBIs in the next Sprint with 50% probability, [some number] with an 85% probability, and [some number] with a 95% probability based on historic throughput. 1

What Common Failure Modes Emerge When Applying Probabilistic Forecasting?

  • Shared Capacity Illusion
    • When capacity forecasts are interpreted without accounting for competing demand and prioritization.
    • Capacity is shared, but expectations are interpreted as dedicated.
    • Probabilistic forecasting in project-based organizations without prioritization creates false confidence.
    • Instead of: “We can complete 21 PBIs” Try: “Given all current priorities, there’s an 85% chance we reach item #18 in the backlog. Project A is #22 thus unlikely this sprint.”

What Dysfunctions are Addressed by Probabilistic Forecasting?

Footnotes

  1. Story Points Are Not the Problem, Velocity Is