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 |  Facilitation Team Charter |  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 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. | 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 | Low | Medium | Low |
Timedifferent | 45-90 min | 30 min Setup, dann laufend | 2-4 h | 45-90 min |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 3-12 | 3-12 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | RAID Log, Status Report Source | Team Charter, Working Norms, Role Notes | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TeamCollaborationAgile | RiskTrackingStakeholdersGovernance | TeamAlignmentCollaboration | AlignmentStakeholdersTeam |