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 |  Product Discovery Jobs to Be Done |  Agile Acceptance Criteria Workshop |  Architecture Risk Storming |
|---|---|---|---|---|
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 switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | 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. | 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 | Low |
Timedifferent | 2-4 h | 1-3 Wochen | 20-40 min pro Story | 60-90 min |
Participantsdifferent | 5-15 | 5-12 Interviews | 3-6 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Job Stories, Outcome Statements, Opportunity List | Acceptance Criteria, Story Update | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | RequirementsArchitectureWorkshop | CustomerOutcomesNeeds | AgileRequirementsRefinementBehavior-Driven Development | RiskArchitectureWorkshopValidation |