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 |  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. | 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. | 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 | Low | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 30-60 min | 45-90 min |
Participantsdifferent | 3-10 (Scrum Team) | 3-7 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Map, Acceptance Criteria, Open Questions | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | AgileIterationCadence | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
