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 WSJF |  Delivery Cost of Delay |  Delivery MoSCoW |
|---|---|---|---|---|
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 many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. |
Complexitydifferent | Medium | High | High | Low |
Timedifferent | 1-2 Tage | 45-90 min | 90-180 min | 30-90 min |
Participantsdifferent | 10-50 | 3-10 | 3-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Ranked Backlog, Cost-of-Delay Assumptions | CoD Table, Prioritization Sequence | Prioritized Backlog, Release Scope, Tradeoff Notes |
Tags1 shared | SatisfactionPrioritizationCustomer | LeanEconomicsSequencePrioritization | PrioritizationDeliveryEconomicsDecision | PrioritizationScopeDecision |