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 WorkshopThree AmigosArchitecture Decision RecordSpecification by Example
| Criterion |  Agile Acceptance Criteria Workshop |  Agile Three Amigos |  Architecture Architecture Decision Record |  Agile Specification by Example |
|---|---|---|---|---|
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 story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 20-40 min pro Story | 15-30 min | 15-45 min | 60-90 min pro Feature |
Participantsdifferent | 3-6 | 3 | 1-3 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Acceptance Criteria, Story Update | Clarified Story, Test Examples, Open Questions | ADR File, Decision Log, Rationale | Example Table, Acceptance Tests |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | CollaborationBehavior-Driven DevelopmentQualityRefinement | ArchitectureRationaleDocumentationGovernance | AgileRequirementsExamplesBehavior-Driven Development |