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