View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Evaporating Cloud |  Agile Ideal Days |  Agile Planning Poker |  Facilitation Dot Estimation |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 60-120 min | 15-60 min | 2-5 min je Item | 5-20 min |
Participantsdifferent | 2-8 | 2-9 | 3-9 | 3-20 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Relative Estimates, Assumption Notes, Split Candidates | Effort Heatmap, Risk Signals, Discussion Targets |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | EstimationEffortAgile | EstimationAgileRelative sizingTeam | EstimationEffortRisk |