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 | ![]() Decision Making Wideband Delphi | ![]() Engineering Kanban |
|---|---|---|---|---|
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. | A single opinion rarely holds up for planning when the future is genuinely uncertain. It separates options, evaluation criteria, and open risks. The result is captured as an Estimate Range, Assumption Log, and Expert Consensus Notes. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. |
Complexitydifferent | High | Low | High | Medium |
Timedifferent | 30-90 min Setup, danach laufend | 5-20 min | 1-4 h or multiple rounds | Ongoing |
Participantsdifferent | 1-8 | 3-20 | 4-12 Experten | 2-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | Effort Heatmap, Risk Signals, Discussion Targets | Estimate Range, Assumption Log, Expert Consensus Notes | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | ForecastingFlowDelivery | EstimationEffortRisk | EstimationExpertsForecasting | FlowVisual managementDelivery |



