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 Future Reality Tree |  Agile Specification by Example |  Systems Thinking Evaporating Cloud |
|---|---|---|---|---|
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. | 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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 2-4 h | 60-90 min pro Feature | 60-120 min |
Participantsdifferent | 3-10 (Scrum Team) | 3-8 | 3-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Example Table, Acceptance Tests | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tagsno overlap | AgileIterationCadence | Theory of ConstraintsSystems thinkingChange | AgileRequirementsExamplesBehavior-Driven Development | Theory of ConstraintsAssumptionsSystems thinking |