View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Monte Carlo Forecasting |  Facilitation Dot Estimation |  Systems Thinking Evaporating Cloud |  Agile NoEstimates |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. | When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. |
Complexitydifferent | High | Low | Medium | Medium |
Timedifferent | 30-90 min Setup, danach laufend | 5-20 min | 60-120 min | laufend |
Participantsdifferent | 1-8 | 3-20 | 2-8 | 2-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | Effort Heatmap, Risk Signals, Discussion Targets | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Throughput Data, Flow Forecast, Slicing Rules |
Tagsno overlap | ForecastingFlowDelivery | EstimationEffortRisk | Theory of ConstraintsAssumptionsSystems thinking | EstimationForecastingFlow |