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 Example Mapping |  Agile Working Agreements |  Agile Three Amigos |  Facilitation Team Charter |
|---|---|---|---|---|
Purposedifferent | 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 collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | 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 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 | 30-60 min | 45-90 min | 15-30 min | 2-4 h |
Participantsdifferent | 3-7 | 3-12 | 3 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Working Agreements, Team Norms, Review Cadence | Clarified Story, Test Examples, Open Questions | Team Charter, Working Norms, Role Notes |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | TeamCollaborationAgile | CollaborationBehavior-Driven DevelopmentQualityRefinement | TeamAlignmentCollaboration |