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 |  Agile ROAM Board |  Facilitation Expectation Mapping |  Facilitation Team Charter |
|---|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45-90 min | 20-40 min initial, dann laufend | 45-90 min | 2-4 h |
Participantsdifferent | 3-12 | 3-15 | 3-12 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | ROAM Board, Owner List | Expectation Map, Alignment Notes, Agreements | Team Charter, Working Norms, Role Notes |
Tagsno overlap | TeamCollaborationAgile | RiskAgileTrackingAlignment | AlignmentStakeholdersTeam | TeamAlignmentCollaboration |