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 | ![]() Knowledge Modeling IBIS | ![]() Decision Making Cynefin Workshop | ![]() Delivery MoSCoW |
|---|---|---|---|---|
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. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. | 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 | Medium | Medium | Medium | Low |
Timedifferent | 2-4 h | 1-3 h | 60-180 min | 30-90 min |
Participantsdifferent | 2-8 | 2-8 | 4-20 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Issue Map, Positions, Argument Notes | Cynefin Map, Domain-specific Actions, Sensemaking Notes | Prioritized Backlog, Release Scope, Tradeoff Notes |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | RationaleKnowledgeDecision | ComplexitySensemakingDecision | PrioritizationScopeDecision |



