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 |  Facilitation Team Charter |  Agile Affinity Estimation |  Agile Planning Poker |
|---|---|---|---|---|
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 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 many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 90-180 min | 2-4 h | 30-90 min | 2-5 min je Item |
Participantsdifferent | 5-15 | 3-12 | 3-12 | 3-9 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Spotify Model Map, Action List | Team Charter, Working Norms, Role Notes | Affinity Size Map, Grouped Estimates, Unclear Items | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | TeamAlignmentCollaboration | EstimationBacklogRelative sizing | EstimationAgileRelative sizingTeam |