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 |  Decision Making Argument 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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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 | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-3 h | 45-90 min |
Participantsdifferent | 3-10 (Scrum Team) | 1-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Argument Map, Evidence Gaps, Decision Rationale | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | AgileIterationCadence | SensemakingDecisionRationale | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
