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 Specification by Example |  Facilitation Team Charter |  Agile Working Agreements |
|---|---|---|---|---|
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 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 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. | When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 90-180 min | 60-90 min pro Feature | 2-4 h | 45-90 min |
Participantsdifferent | 5-15 | 3-6 | 3-12 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | Example Table, Acceptance Tests | Team Charter, Working Norms, Role Notes | Working Agreements, Team Norms, Review Cadence |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | AgileRequirementsExamplesBehavior-Driven Development | TeamAlignmentCollaboration | TeamCollaborationAgile |