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 Affinity Estimation |  Product Discovery Jobs to Be Done |  Product Discovery Kano Model |  Agile Planning Poker |
|---|---|---|---|---|
Purposedifferent | 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 switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 30-90 min | 1-3 Wochen | 1-2 Tage | 2-5 min je Item |
Participantsdifferent | 3-12 | 5-12 Interviews | 10-50 | 3-9 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Affinity Size Map, Grouped Estimates, Unclear Items | Job Stories, Outcome Statements, Opportunity List | Kano Matrix, Feature Classes, Priority Themes | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | EstimationBacklogRelative sizing | CustomerOutcomesNeeds | SatisfactionPrioritizationCustomer | EstimationAgileRelative sizingTeam |