View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Risk StormingATAM (Architecture Tradeoff Analysis Method)Specification by ExampleAcceptance Criteria Workshop
| Criterion |  Architecture Risk Storming |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Agile Specification by Example |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 60-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 60-90 min pro Feature | 20-40 min pro Story |
Participantsdifferent | 4-12 | Evaluation team, architects, and relevant stakeholders | 3-6 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | 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 | Example Table, Acceptance Tests | Acceptance Criteria, Story Update |
Tagsno overlap | RiskArchitectureWorkshopValidation | ArchitectureQualityRiskTradeoffsStakeholders | AgileRequirementsExamplesBehavior-Driven Development | AgileRequirementsRefinementBehavior-Driven Development |