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 |  Agile Specification by Example |  Systems Thinking Future Reality Tree |  Systems Thinking Intervention Mapping |
|---|---|---|---|---|
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. | 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. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | 1-4 Wochen je Sprint, laufend | 60-90 min pro Feature | 2-4 h | 1-5 Tage |
Participantsdifferent | 3-10 (Scrum Team) | 3-6 | 3-8 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Table, Acceptance Tests | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Logic Model, Change Objectives, Intervention Components, Evaluation Plan |
Tagsno overlap | AgileIterationCadence | AgileRequirementsExamplesBehavior-Driven Development | Theory of ConstraintsSystems thinkingChange | ChangeSystems thinkingCapability |