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 Example Mapping |  Knowledge Modeling Competency Questions |  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 a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 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 | Low | Medium | Low |
Timedifferent | 1-2 Tage | 30-60 min | 2-4 h | 30-90 min |
Participantsdifferent | 10-50 | 3-7 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Example Map, Acceptance Criteria, Open Questions | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Prioritized Backlog, Release Scope, Tradeoff Notes |
Tagsno overlap | SatisfactionPrioritizationCustomer | Behavior-Driven DevelopmentRequirementsExamplesRefinement | OntologyKnowledge graphScopeRequirementsSemantic | PrioritizationScopeDecision |