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 |  Architecture Risk Storming |  Agile Specification by Example |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 15-30 min | 60-90 min | 60-90 min pro Feature | 45-60 min |
Participantsdifferent | 3 | 4-12 | 3-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Clarified Story, Test Examples, Open Questions | Annotated Diagram, Prioritized Risk List, Action Backlog | Example Table, Acceptance Tests | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | CollaborationBehavior-Driven DevelopmentQualityRefinement | RiskArchitectureWorkshopValidation | AgileRequirementsExamplesBehavior-Driven Development | AssumptionsRiskExperimentsValidation |