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 Story Points |  Team Design Team Topologies Interaction Modes |  Facilitation Expectation Mapping |  Team Design Spotify Model Mapping |
|---|---|---|---|---|
Purposedifferent | When teams want to rate complexity rather than hours, it creates a shared, relative scale. It sorts work by value, risk, and delivery ability. The result is captured as Point Estimates, Reference Stories, and Velocity Data. | 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. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | laufend, 1-5 min je Item | Half day | 45-90 min | 90-180 min |
Participantsdifferent | 3-9 | Team-Leads plus Architecture | 3-12 | 5-15 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Interaction Heat Map, Agreements per Pair | Expectation Map, Alignment Notes, Agreements | Spotify Model Map, Action List |
Tagsno overlap | EstimationAgileMeasurement | TeamAlignmentCollaborationOrganization | AlignmentStakeholdersTeam | TeamOrganizationAlignmentDiagnosis |