View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Competency Questions |  Delivery MoSCoW |  Product Strategy ICE Scoring |  Knowledge Modeling NeOn Methodology |
|---|---|---|---|---|
Purposedifferent | 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. | When ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list. | The NeOn Methodology structures ontology work as a controlled process with reuse, scenarios, and reviews. It is useful when ontologies should not emerge ad hoc but modularly and reusably. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 2-4 h | 30-90 min | 30-60 min | Mehrere Wochen bis Monate |
Participantsdifferent | 2-8 | 3-12 | 2-8 | 2-10 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Prioritized Backlog, Release Scope, Tradeoff Notes | ICE Table, Top Idea List | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | PrioritizationScopeDecision | PrioritizationScoringGrowthDecision | OntologyMethodologyReuseSemanticEngineering |