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 Scrum |  Architecture Architecture Decision Record |  Agile Specification by Example |  Architecture Quality Attribute Workshop |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 15-45 min | 60-90 min pro Feature | 2-4 h |
Participantsdifferent | 3-10 (Scrum Team) | 1-3 | 3-6 | 5-15 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | ADR File, Decision Log, Rationale | Example Table, Acceptance Tests | Quality Scenarios, Priority List, Architecture Concerns |
Tagsno overlap | AgileIterationCadence | ArchitectureRationaleDocumentationGovernance | AgileRequirementsExamplesBehavior-Driven Development | RequirementsArchitectureWorkshop |