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 Example Mapping |  Team Design Spotify Model Mapping |  Agile Specification by Example |
|---|---|---|---|---|
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 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 a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 15-30 min | 30-60 min | 90-180 min | 60-90 min pro Feature |
Participantsdifferent | 3 | 3-7 | 5-15 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Clarified Story, Test Examples, Open Questions | Example Map, Acceptance Criteria, Open Questions | Spotify Model Map, Action List | Example Table, Acceptance Tests |
Tagsno overlap | CollaborationBehavior-Driven DevelopmentQualityRefinement | Behavior-Driven DevelopmentRequirementsExamplesRefinement | TeamOrganizationAlignmentDiagnosis | AgileRequirementsExamplesBehavior-Driven Development |