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 Team Topologies Interaction Modes |  Agile ROAM Board |  Facilitation Expectation Mapping |
|---|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | Half day | 20-40 min initial, dann laufend | 45-90 min |
Participantsdifferent | 3-12 | Team-Leads plus Architecture | 3-15 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | Interaction Heat Map, Agreements per Pair | ROAM Board, Owner List | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TeamCollaborationAgile | TeamAlignmentCollaborationOrganization | RiskAgileTrackingAlignment | AlignmentStakeholdersTeam |