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 Specification by Example |  Decision Making Argument Mapping |  Architecture Request for Comments |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | 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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 | Medium | Medium | Low |
Timedifferent | 60-90 min pro Feature | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung | 20-40 min pro Story |
Participantsdifferent | 3-6 | 1-8 | 3-20 Reviewer | 3-6 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Argument Map, Evidence Gaps, Decision Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Acceptance Criteria, Story Update |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | SensemakingDecisionRationale | ArchitectureDecisionAsyncGovernance | AgileRequirementsRefinementBehavior-Driven Development |