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 Shape-First Modeling |  Delivery MoSCoW |  Decision Making Decision Matrix |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | 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. | 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 several options collide with several criteria, comparison quickly becomes subjective. A Decision Matrix makes the trade-off visible and brings weighting, criteria, and options into a shared logic. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | Halber Tag pro Domain Slice | 30-90 min | 45-90 min | 2-4 h |
Participantsdifferent | 1-4 | 3-12 | 2-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Prioritized Backlog, Release Scope, Tradeoff Notes | Decision Matrix, Scoring Rationale, Selected Option | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Knowledge graphValidationSemantic | PrioritizationScopeDecision | DecisionCriteriaScoringTradeoffs | OntologyKnowledge graphScopeRequirementsSemantic |