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 Delegation Poker |  Agile Specification by Example |  Agile Example Mapping |  Facilitation Responsibility Poker |
|---|---|---|---|---|
Purposedifferent | When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice. | 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 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 60-90 min pro Feature | 30-60 min | 45-90 min |
Participantsdifferent | 3-10 | 3-6 | 3-7 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions | Responsibility Map, Role Agreements, Open Questions |
Tagsno overlap | AutonomyRolesTeam | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RolesResponsibilityTeamFacilitation |