View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Acceptance Criteria WorkshopFishbone DiagramATAM (Architecture Tradeoff Analysis Method)Example Mapping
| Criterion |  Agile Acceptance Criteria Workshop |  Operations Fishbone Diagram |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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 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. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 20-40 min pro Story | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min |
Participantsdifferent | 3-6 | 2-8 | Evaluation team, architects, and relevant stakeholders | 3-7 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Acceptance Criteria, Story Update | Fishbone Diagram, Cause Categories, Investigation 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 Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | Root causeQualityOperations | ArchitectureQualityRiskTradeoffsStakeholders | Behavior-Driven DevelopmentRequirementsExamplesRefinement |