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 | ![]() Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
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 several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 15-30 min | 30-60 min | 90-180 min | Half day |
Participantsdifferent | 3 | 3-7 | 5-15 | Team-Leads plus Architecture |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Clarified Story, Test Examples, Open Questions | Example Map, Acceptance Criteria, Open Questions | Spotify Model Map, Action List | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | CollaborationBehavior-Driven DevelopmentQualityRefinement | Behavior-Driven DevelopmentRequirementsExamplesRefinement | TeamOrganizationAlignmentDiagnosis | TeamAlignmentCollaborationOrganization |



