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 Dot Voting | ![]() Agile Specification by Example | ![]() Agile Example Mapping | ![]() Agile Three Amigos |
|---|---|---|---|---|
Purposedifferent | When a workshop has produced too many options and the group needs to condense quickly, dot voting makes preferences visible in a short time. It bundles individual votes into a solid signal for the next selection. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 5-15 min | 60-90 min pro Feature | 30-60 min | 15-30 min |
Participantsdifferent | 3-20 | 3-6 | 3-7 | 3 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Ranked list, Consensus signal, Shortlist | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions | Clarified Story, Test Examples, Open Questions |
Tagsno overlap | FacilitationVotingConsensusPrioritization | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CollaborationBehavior-Driven DevelopmentQualityRefinement |



