View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Delphi Method |  Knowledge Modeling Shape-First Modeling |  Knowledge Modeling Competency Questions |  Delivery MoSCoW |
|---|---|---|---|---|
Purposedifferent | When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start. | 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 | High | Medium | Medium | Low |
Timedifferent | 1-4 Wochen | Halber Tag pro Domain Slice | 2-4 h | 30-90 min |
Participantsdifferent | 6-30 Experten | 1-4 | 2-8 | 3-12 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Expert Forecast, Consensus Range, Assumption Notes | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Prioritized Backlog, Release Scope, Tradeoff Notes |
Tagsno overlap | ForecastingExpertsDecisionStrategy | Knowledge graphValidationSemantic | OntologyKnowledge graphScopeRequirementsSemantic | PrioritizationScopeDecision |