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 Future Reality Tree |  Agile Planning Poker |  Systems Thinking Evaporating Cloud |  Agile Ideal Days |
|---|---|---|---|---|
Purposedifferent | 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. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | 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. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | 2-4 h | 2-5 min je Item | 60-120 min | 15-60 min |
Participantsdifferent | 3-8 | 3-9 | 2-8 | 2-9 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Relative Estimates, Assumption Notes, Split Candidates | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | Theory of ConstraintsSystems thinkingChange | EstimationAgileRelative sizingTeam | Theory of ConstraintsAssumptionsSystems thinking | EstimationEffortAgile |