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 Scrum |  Systems Thinking Evaporating Cloud |  Systems Thinking Future Reality Tree |  Systems Thinking Theory of Constraints Thinking Process |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | The Theory of Constraints Thinking Process exposes a system's bottleneck and the logic behind it. It suits situations where many symptoms trace back to the same limiting relationship. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | 1-4 Wochen je Sprint, laufend | 60-120 min | 2-4 h | 0.5-3 Tage |
Participantsdifferent | 3-10 (Scrum Team) | 2-8 | 3-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Current Reality Logic, Conflict Cloud, Future Reality Tree, Implementation Obstacles |
Tagsno overlap | AgileIterationCadence | Theory of ConstraintsAssumptionsSystems thinking | Theory of ConstraintsSystems thinkingChange | Theory of ConstraintsConstraintsSystems thinkingCausality |