View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile NoEstimates | ![]() Facilitation Dot Estimation | ![]() Systems Thinking Current Reality Tree | ![]() Operations Bottleneck Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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 Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once. | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | laufend | 5-20 min | 2-6 h | 1-3 h |
Participantsdifferent | 2-12 | 3-20 | 3-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Throughput Data, Flow Forecast, Slicing Rules | Effort Heatmap, Risk Signals, Discussion Targets | Current Reality Tree, Core Problems, Intervention Ideas | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures |
Tagsno overlap | EstimationForecastingFlow | EstimationEffortRisk | Systems thinkingRoot causeConstraintsCausality | FlowMeasurementConstraints |



