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 Example Mapping |  Facilitation Responsibility Poker |  Agile Affinity Estimation |
|---|---|---|---|
Purposedifferent | 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. | When many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 30-60 min | 45-90 min | 30-90 min |
Participantsdifferent | 3-7 | 3-10 | 3-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Responsibility Map, Role Agreements, Open Questions | Affinity Size Map, Grouped Estimates, Unclear Items |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RolesResponsibilityTeamFacilitation | EstimationBacklogRelative sizing |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
