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 |  Agile Three Amigos |  Agile Example Mapping |  Agile Specification by Example |
|---|---|---|---|---|
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 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 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 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45-90 min | 15-30 min | 30-60 min | 60-90 min pro Feature |
Participantsdifferent | 3-12 | 3 | 3-7 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Clarified Story, Test Examples, Open Questions | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests |
Tagsno overlap | AlignmentStakeholdersTeam | CollaborationBehavior-Driven DevelopmentQualityRefinement | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development |