View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Kano Model |  Agile Planning Poker |  Agile Affinity Estimation |  Agile T-Shirt Sizing |
|---|---|---|---|---|
Purposedifferent | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | 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. | When effort only needs to be classified roughly, it makes comparability more important than false precision. It helps sort work quickly into manageable sizes. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-2 Tage | 2-5 min je Item | 30-90 min | 15-45 min |
Participantsdifferent | 10-50 | 3-9 | 3-12 | 2-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Relative Estimates, Assumption Notes, Split Candidates | Affinity Size Map, Grouped Estimates, Unclear Items | Size Buckets, Rough Backlog Map, Split Candidates |
Tagsno overlap | SatisfactionPrioritizationCustomer | EstimationAgileRelative sizingTeam | EstimationBacklogRelative sizing | EstimationAgileRoadmap |