View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Team Charter |  Delivery RAID Log |  Team Design Team Topologies Interaction Modes |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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 | Medium | Low | Medium | Low |
Timedifferent | 2-4 h | 30 min Setup, dann laufend | Half day | 20-40 min initial, dann laufend |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | Team-Leads plus Architecture | 3-15 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Team Charter, Working Norms, Role Notes | RAID Log, Status Report Source | Interaction Heat Map, Agreements per Pair | ROAM Board, Owner List |
Tagsno overlap | TeamAlignmentCollaboration | RiskTrackingStakeholdersGovernance | TeamAlignmentCollaborationOrganization | RiskAgileTrackingAlignment |