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 Dot Voting |  Delivery MoSCoW |  Facilitation Consensus Workshop |
|---|---|---|---|---|
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 workshop has produced too many options and the group needs to condense quickly, dot voting makes preferences visible in a short time. It bundles individual votes into a solid signal for the next selection. | 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 a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 2-4 h | 5-15 min | 30-90 min | 1-3 h |
Participantsdifferent | 2-8 | 3-20 | 3-12 | 5-30 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Ranked list, Consensus signal, Shortlist | Prioritized Backlog, Release Scope, Tradeoff Notes | Consensus Clusters, Theme Titles, Priority Areas |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | FacilitationVotingConsensusPrioritization | PrioritizationScopeDecision | FacilitationConsensusWorkshopAlignment |