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 Example Mapping | ![]() Systems Thinking Leverage Points | ![]() Systems Thinking Future Reality Tree |
|---|---|---|---|---|
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 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. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | 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. |
Complexitydifferent | Medium | Low | High | High |
Timedifferent | 1-4 Wochen je Sprint, laufend | 30-60 min | Half day | 2-4 h |
Participantsdifferent | 3-10 (Scrum Team) | 3-7 | 3-12 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Map, Acceptance Criteria, Open Questions | Leverage Map, Action Strategy | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | AgileIterationCadence | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Systems thinkingChangeStrategy | Theory of ConstraintsSystems thinkingChange |



