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 Specification by Example |  Decision Making Argument Mapping |
|---|---|---|---|
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 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 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 60-90 min pro Feature | 1-3 h |
Participantsdifferent | 3-10 (Scrum Team) | 3-6 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Table, Acceptance Tests | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | AgileIterationCadence | AgileRequirementsExamplesBehavior-Driven Development | SensemakingDecisionRationale |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
