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 |  Delivery RAID Log |  Agile Acceptance Criteria Workshop |  Agile Specification by Example |
|---|---|---|---|---|
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. | 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 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 15-45 min | 30 min Setup, dann laufend | 20-40 min pro Story | 60-90 min pro Feature |
Participantsdifferent | 1-3 | 1-3 maintaining, briefing for everyone | 3-6 | 3-6 |
Formatdifferent | Async | Async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Acceptance Criteria, Story Update | Example Table, Acceptance Tests |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | AgileRequirementsRefinementBehavior-Driven Development | AgileRequirementsExamplesBehavior-Driven Development |