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 |  Delivery RAID Log |  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. | 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 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 30 min Setup, dann laufend | 20-40 min initial, dann laufend | 45-90 min |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 3-15 | 3-12 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | RAID Log, Status Report Source | ROAM Board, Owner List | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TeamCollaborationAgile | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment | AlignmentStakeholdersTeam |