View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Spotify Model Mapping |  Agile Example Mapping |  Agile Three Amigos |  Facilitation Team Charter |
|---|---|---|---|---|
Purposedifferent | 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 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 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 team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 90-180 min | 30-60 min | 15-30 min | 2-4 h |
Participantsdifferent | 5-15 | 3-7 | 3 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Spotify Model Map, Action List | Example Map, Acceptance Criteria, Open Questions | Clarified Story, Test Examples, Open Questions | Team Charter, Working Norms, Role Notes |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CollaborationBehavior-Driven DevelopmentQualityRefinement | TeamAlignmentCollaboration |