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 Specification by Example |  Facilitation Responsibility Poker |  Agile Affinity Estimation |
|---|---|---|---|
Purposedifferent | 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 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 | Medium | Low | Medium |
Timedifferent | 60-90 min pro Feature | 45-90 min | 30-90 min |
Participantsdifferent | 3-6 | 3-10 | 3-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Responsibility Map, Role Agreements, Open Questions | Affinity Size Map, Grouped Estimates, Unclear Items |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | RolesResponsibilityTeamFacilitation | EstimationBacklogRelative sizing |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
