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 Quality Attribute Workshop |  Agile Specification by Example |  Decision Making DACI |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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 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. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 2-4 h | 60-90 min pro Feature | 30-60 min | 30-60 min |
Participantsdifferent | 5-15 | 3-6 | 2-10 | 3-7 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Example Table, Acceptance Tests | DACI Matrix, Decision Owner, Decision Log | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | RequirementsArchitectureWorkshop | AgileRequirementsExamplesBehavior-Driven Development | DecisionRolesGovernanceAlignment | Behavior-Driven DevelopmentRequirementsExamplesRefinement |