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)Fishbone DiagramSpecification by Example
| Criterion |  Agile Example Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Fishbone Diagram |  Agile Specification by Example |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Low | High | Low | Medium |
Timedifferent | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min | 60-90 min pro Feature |
Participantsdifferent | 3-7 | Evaluation team, architects, and relevant stakeholders | 2-8 | 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 | Fishbone Diagram, Cause Categories, Investigation Backlog | Example Table, Acceptance Tests |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureQualityRiskTradeoffsStakeholders | Root causeQualityOperations | AgileRequirementsExamplesBehavior-Driven Development |