View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery MoSCoW |  Growth A/B Testing |  Knowledge Modeling Competency Questions |  Knowledge Modeling Shape-First Modeling |
|---|---|---|---|---|
Purposedifferent | 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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. | 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. | 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. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 30-90 min | 1-4 Wochen | 2-4 h | Halber Tag pro Domain Slice |
Participantsdifferent | 3-12 | 1-6 | 2-8 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized Backlog, Release Scope, Tradeoff Notes | Experiment results, Decision log, Learning summary | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation |
Tagsno overlap | PrioritizationScopeDecision | ExperimentsGrowthAnalyticsValidation | OntologyKnowledge graphScopeRequirementsSemantic | Knowledge graphValidationSemantic |