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 WSJF |  Architecture Risk Storming |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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 many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. |
Complexitydifferent | Medium | High | Low | High |
Timedifferent | 2-4 h | 45-90 min | 60-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 5-15 | 3-10 | 4-12 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Ranked Backlog, Cost-of-Delay Assumptions | Annotated Diagram, Prioritized Risk List, Action Backlog | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | RequirementsArchitectureWorkshop | LeanEconomicsSequencePrioritization | RiskArchitectureWorkshopValidation | ArchitectureQualityRiskTradeoffsStakeholders |