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 | ![]() Systems Thinking Evaporating Cloud | ![]() Facilitation Dot Estimation | ![]() Systems Thinking Future Reality Tree |
|---|---|---|---|---|
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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | laufend | 60-120 min | 5-20 min | 2-4 h |
Participantsdifferent | 2-12 | 2-8 | 3-20 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Throughput Data, Flow Forecast, Slicing Rules | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Effort Heatmap, Risk Signals, Discussion Targets | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | EstimationForecastingFlow | Theory of ConstraintsAssumptionsSystems thinking | EstimationEffortRisk | Theory of ConstraintsSystems thinkingChange |



