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 |  Facilitation Expectation Mapping |  Agile Three Amigos |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
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 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 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30-60 min | 45-90 min | 15-30 min | Half day |
Participantsdifferent | 3-7 | 3-12 | 3 | Team-Leads plus Architecture |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Expectation Map, Alignment Notes, Agreements | Clarified Story, Test Examples, Open Questions | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AlignmentStakeholdersTeam | CollaborationBehavior-Driven DevelopmentQualityRefinement | TeamAlignmentCollaborationOrganization |