View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Example MappingSpecification by ExampleArchitecture Decision RecordAcceptance Criteria Workshop
| Criterion |  Agile Example Mapping |  Agile Specification by Example |  Architecture Architecture Decision Record |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Low | Medium | Low | Low |
Timedifferent | 30-60 min | 60-90 min pro Feature | 15-45 min | 20-40 min pro Story |
Participantsdifferent | 3-7 | 3-6 | 1-3 | 3-6 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests | ADR File, Decision Log, Rationale | Acceptance Criteria, Story Update |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureRationaleDocumentationGovernance | AgileRequirementsRefinementBehavior-Driven Development |