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 |  Facilitation Team Charter |  Agile Three Amigos |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
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 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 story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 2-4 h | 15-30 min | 20-40 min pro Story |
Participantsdifferent | 3-12 | 3-12 | 3 | 3-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Team Charter, Working Norms, Role Notes | Clarified Story, Test Examples, Open Questions | Acceptance Criteria, Story Update |
Tagsno overlap | AlignmentStakeholdersTeam | TeamAlignmentCollaboration | CollaborationBehavior-Driven DevelopmentQualityRefinement | AgileRequirementsRefinementBehavior-Driven Development |