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 Working Agreements | ![]() Team Design Spotify Model Mapping | ![]() Facilitation Dot Estimation | ![]() Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | 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 size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 90-180 min | 5-20 min | 20-40 min initial, dann laufend |
Participantsdifferent | 3-12 | 5-15 | 3-20 | 3-15 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | Spotify Model Map, Action List | Effort Heatmap, Risk Signals, Discussion Targets | ROAM Board, Owner List |
Tagsno overlap | TeamCollaborationAgile | TeamOrganizationAlignmentDiagnosis | EstimationEffortRisk | RiskAgileTrackingAlignment |



