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 | ![]() Facilitation Decision Jam | ![]() Delivery MoSCoW | ![]() Delivery Cost of Delay |
|---|---|---|---|---|
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 decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. | 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. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 2-4 h | 60-90 min | 30-90 min | 90-180 min |
Participantsdifferent | 2-8 | 4-10 | 3-12 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Problem Cluster, Prioritized Challenge, Experiment | Prioritized Backlog, Release Scope, Tradeoff Notes | CoD Table, Prioritization Sequence |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | FacilitationDecisionProblem solvingWorkshop | PrioritizationScopeDecision | PrioritizationDeliveryEconomicsDecision |



