View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Engineering Kanban | ![]() Facilitation Dot Estimation | ![]() Decision Making Delphi Method | ![]() Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | 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. |
Complexitydifferent | Medium | Low | High | High |
Timedifferent | Ongoing | 5-20 min | 1-4 Wochen | 30-90 min Setup, danach laufend |
Participantsdifferent | 2-12 | 3-20 | 6-30 Experten | 1-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Effort Heatmap, Risk Signals, Discussion Targets | Expert Forecast, Consensus Range, Assumption Notes | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | FlowVisual managementDelivery | EstimationEffortRisk | ForecastingExpertsDecisionStrategy | ForecastingFlowDelivery |



