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 Leverage Points |  Agile Acceptance Criteria Workshop |  Decision Making Force Field Analysis |
|---|---|---|---|---|
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. | 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. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | Half day | 20-40 min pro Story | 45-90 min |
Participantsdifferent | 3-10 (Scrum Team) | 3-12 | 3-6 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Leverage Map, Action Strategy | Acceptance Criteria, Story Update | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | AgileIterationCadence | Systems thinkingChangeStrategy | AgileRequirementsRefinementBehavior-Driven Development | ChangeDecisionStrategy |