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 |  Knowledge Modeling Competency Questions |  Agile Specification by Example |  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. | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | 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 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 | Medium | Medium | Low |
Timedifferent | 1-2 Tage | 2-4 h | 60-90 min pro Feature | 30-90 min |
Participantsdifferent | 10-50 | 2-8 | 3-6 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Example Table, Acceptance Tests | Prioritized Backlog, Release Scope, Tradeoff Notes |
Tagsno overlap | SatisfactionPrioritizationCustomer | OntologyKnowledge graphScopeRequirementsSemantic | AgileRequirementsExamplesBehavior-Driven Development | PrioritizationScopeDecision |