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 |  Decision Making Three-Point Estimation |  Facilitation Dot Estimation |  Agile NoEstimates |
|---|---|---|---|---|
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. | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes. | 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 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 | Medium | Medium | Low | Medium |
Timedifferent | Ongoing | 10-30 min je Item | 5-20 min | laufend |
Participantsdifferent | 2-12 | 1-8 | 3-20 | 2-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Three-Point Estimate, Risk Range, Assumption Notes | Effort Heatmap, Risk Signals, Discussion Targets | Throughput Data, Flow Forecast, Slicing Rules |
Tagsno overlap | FlowVisual managementDelivery | EstimationUncertaintyForecasting | EstimationEffortRisk | EstimationForecastingFlow |