View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Specification by ExampleARID (Active Reviews for Intermediate Designs)Three AmigosATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Agile Specification by Example |  Architecture ARID (Active Reviews for Intermediate Designs) |  Agile Three Amigos |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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. | 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 | Medium | Medium | Low | High |
Timedifferent | 60-90 min pro Feature | 2–4 h review as a planning range; preparation and evaluation additional | 15-30 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-6 | Designers, developers as users, and facilitation | 3 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Clarified Story, Test Examples, 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 | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureEngineeringFeedbackValidationTasks | CollaborationBehavior-Driven DevelopmentQualityRefinement | ArchitectureQualityRiskTradeoffsStakeholders |