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 Team Charter |  Agile Three Amigos |  Team Design Team Topologies Interaction Modes |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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 several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 2-4 h | 15-30 min | Half day | 30-60 min |
Participantsdifferent | 3-12 | 3 | Team-Leads plus Architecture | 3-7 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | Clarified Story, Test Examples, Open Questions | Interaction Heat Map, Agreements per Pair | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | TeamAlignmentCollaboration | CollaborationBehavior-Driven DevelopmentQualityRefinement | TeamAlignmentCollaborationOrganization | Behavior-Driven DevelopmentRequirementsExamplesRefinement |