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 Acceptance Criteria Workshop |  Agile Specification by Example |  Architecture Architecture Decision Record |  Architecture arc42 |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 20-40 min pro Story | 60-90 min pro Feature | 15-45 min | 1-2 Tage |
Participantsdifferent | 3-6 | 3-6 | 1-3 | 1-4 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Acceptance Criteria, Story Update | Example Table, Acceptance Tests | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |