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 Specification by Example |  Systems Thinking Future Reality Tree |  Systems Thinking Evaporating Cloud |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 60-90 min pro Feature | 2-4 h | 60-120 min | 30-60 min |
Participantsdifferent | 3-6 | 3-8 | 2-8 | 3-7 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Theory of ConstraintsSystems thinkingChange | Theory of ConstraintsAssumptionsSystems thinking | Behavior-Driven DevelopmentRequirementsExamplesRefinement |