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