View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Three AmigosSAAM (Software Architecture Analysis Method)Example MappingATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Agile Three Amigos |  Architecture SAAM (Software Architecture Analysis Method) |  Agile Example Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | 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. |
Complexitydifferent | Low | High | Low | High |
Timedifferent | 15-30 min | Preparation, scenario analysis, and findings review; effort depends on scope | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3 | Architecture experts and stakeholders for scenarios and weighting | 3-7 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Clarified Story, Test Examples, Open Questions | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | 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 |
Tagsno overlap | CollaborationBehavior-Driven DevelopmentQualityRefinement | ArchitectureChangeAnalysisComparisonQuality | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureQualityRiskTradeoffsStakeholders |