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 Three Amigos |  Facilitation Expectation Mapping |  Agile Specification by Example |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
Purposedifferent | 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 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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 | Medium | Medium |
Timedifferent | 15-30 min | 45-90 min | 60-90 min pro Feature | Half day |
Participantsdifferent | 3 | 3-12 | 3-6 | Team-Leads plus Architecture |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Clarified Story, Test Examples, Open Questions | Expectation Map, Alignment Notes, Agreements | Example Table, Acceptance Tests | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | CollaborationBehavior-Driven DevelopmentQualityRefinement | AlignmentStakeholdersTeam | AgileRequirementsExamplesBehavior-Driven Development | TeamAlignmentCollaborationOrganization |