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 Responsibility Poker |  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 it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 15-30 min | 45-90 min | 30-60 min |
Participantsdifferent | 3 | 3-10 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Clarified Story, Test Examples, Open Questions | Responsibility Map, Role Agreements, Open Questions | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | CollaborationBehavior-Driven DevelopmentQualityRefinement | RolesResponsibilityTeamFacilitation | Behavior-Driven DevelopmentRequirementsExamplesRefinement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
