View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Example MappingATAM (Architecture Tradeoff Analysis Method)Quality Attribute WorkshopAcceptance Criteria Workshop
| Criterion | ![]() Agile Example Mapping | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Architecture Quality Attribute Workshop | ![]() Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 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 | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope | 2-4 h | 20-40 min pro Story |
Participantsdifferent | 3-7 | Evaluation team, architects, and relevant stakeholders | 5-15 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Quality Scenarios, Priority List, Architecture Concerns | Acceptance Criteria, Story Update |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureQualityRiskTradeoffsStakeholders | RequirementsArchitectureWorkshop | AgileRequirementsRefinementBehavior-Driven Development |



