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 Expectation Mapping |  Agile Working Agreements |  Agile Example Mapping |  Facilitation Team Charter |
|---|---|---|---|---|
Purposedifferent | 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 collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 | 45-90 min | 30-60 min | 2-4 h |
Participantsdifferent | 3-12 | 3-12 | 3-7 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Working Agreements, Team Norms, Review Cadence | Example Map, Acceptance Criteria, Open Questions | Team Charter, Working Norms, Role Notes |
Tagsno overlap | AlignmentStakeholdersTeam | TeamCollaborationAgile | Behavior-Driven DevelopmentRequirementsExamplesRefinement | TeamAlignmentCollaboration |