View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Agile Acceptance Criteria Workshop | ![]() Agile Three Amigos |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 15-45 min | 20-40 min pro Story | 15-30 min |
Participantsdifferent | 1-3 | 3-6 | 3 |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Acceptance Criteria, Story Update | Clarified Story, Test Examples, Open Questions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | AgileRequirementsRefinementBehavior-Driven Development | CollaborationBehavior-Driven DevelopmentQualityRefinement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






