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 ROAM Board |  Delivery RAID Log |  Team Design Team Topologies Interaction Modes |  Team Design Spotify Model Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 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 | Low | Low | Medium | Medium |
Timedifferent | 20-40 min initial, dann laufend | 30 min Setup, dann laufend | Half day | 90-180 min |
Participantsdifferent | 3-15 | 1-3 maintaining, briefing for everyone | Team-Leads plus Architecture | 5-15 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | ROAM Board, Owner List | RAID Log, Status Report Source | Interaction Heat Map, Agreements per Pair | Spotify Model Map, Action List |
Tagsno overlap | RiskAgileTrackingAlignment | RiskTrackingStakeholdersGovernance | TeamAlignmentCollaborationOrganization | TeamOrganizationAlignmentDiagnosis |