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 |  Architecture Architecture Decision Record |  Delivery RAID Log |  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. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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-45 min | 30 min Setup, dann laufend | 60-90 min pro Feature |
Participantsdifferent | 3-6 | 1-3 | 1-3 maintaining, briefing for everyone | 3-6 |
Formatdifferent | Workshop | Async | Async | Workshop |
Outputdifferent | Acceptance Criteria, Story Update | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Example Table, Acceptance Tests |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | AgileRequirementsExamplesBehavior-Driven Development |