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 |  Architecture Architecture Decision Record |  Decision Making Decision Rights Mapping |  Agile Example Mapping |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 60-90 min pro Feature | 15-45 min | 90-180 min | 30-60 min |
Participantsdifferent | 3-6 | 1-3 | 4-12 | 3-7 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | ADR File, Decision Log, Rationale | Decision Rights Matrix, Agreement | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureRationaleDocumentationGovernance | DecisionGovernanceAlignmentResponsibility | Behavior-Driven DevelopmentRequirementsExamplesRefinement |