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 Specification by Example |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | Half day | 60-90 min pro Feature | 20-40 min pro Story |
Participantsdifferent | 3-10 (Scrum Team) | 3-12 | 3-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Leverage Map, Action Strategy | Example Table, Acceptance Tests | Acceptance Criteria, Story Update |
Tagsno overlap | AgileIterationCadence | Systems thinkingChangeStrategy | AgileRequirementsExamplesBehavior-Driven Development | AgileRequirementsRefinementBehavior-Driven Development |