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 Responsibility Poker |  Agile Example Mapping |  Agile Planning Poker |
|---|---|---|---|
Purposedifferent | 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. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitysame | Low | Low | Low |
Timedifferent | 45-90 min | 30-60 min | 2-5 min je Item |
Participantsdifferent | 3-10 | 3-7 | 3-9 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Example Map, Acceptance Criteria, Open Questions | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | RolesResponsibilityTeamFacilitation | Behavior-Driven DevelopmentRequirementsExamplesRefinement | EstimationAgileRelative sizingTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
