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 Specification by Example |  Architecture Quality Attribute Workshop |  Architecture Risk Storming |
|---|---|---|---|
Purposedifferent | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 60-90 min pro Feature | 2-4 h | 60-90 min |
Participantsdifferent | 3-6 | 5-15 | 4-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Quality Scenarios, Priority List, Architecture Concerns | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | RequirementsArchitectureWorkshop | RiskArchitectureWorkshopValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
