View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordExample MappingQuality Attribute WorkshopAcceptance Criteria Workshop
| Criterion |  Architecture Architecture Decision Record |  Agile Example Mapping |  Architecture Quality Attribute Workshop |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
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 carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 30-60 min | 2-4 h | 20-40 min pro Story |
Participantsdifferent | 1-3 | 3-7 | 5-15 | 3-6 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Example Map, Acceptance Criteria, Open Questions | Quality Scenarios, Priority List, Architecture Concerns | Acceptance Criteria, Story Update |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RequirementsArchitectureWorkshop | AgileRequirementsRefinementBehavior-Driven Development |