View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile Three Amigos | ![]() Agile Specification by Example | ![]() Architecture SAAM (Software Architecture 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. | 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. | 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. |
Complexitydifferent | Low | Medium | High |
Timedifferent | 15-30 min | 60-90 min pro Feature | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 3 | 3-6 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Clarified Story, Test Examples, Open Questions | Example Table, Acceptance Tests | 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 |
Tagsno overlap | CollaborationBehavior-Driven DevelopmentQualityRefinement | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






