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 ATAM (Architecture Tradeoff Analysis Method) |  Agile Example Mapping |  Agile Three Amigos |
|---|---|---|---|
Purposedifferent | 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. | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. |
Complexitydifferent | High | Low | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min | 15-30 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-7 | 3 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | 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 | Clarified Story, Test Examples, Open Questions |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CollaborationBehavior-Driven DevelopmentQualityRefinement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
