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 |  Delivery MoSCoW |  Facilitation Consensus Workshop |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 2-4 h | 30-90 min | 1-3 h | 1-2 h |
Participantsdifferent | 2-8 | 3-12 | 5-30 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Prioritized Backlog, Release Scope, Tradeoff Notes | Consensus Clusters, Theme Titles, Priority Areas | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | PrioritizationScopeDecision | FacilitationConsensusWorkshopAlignment | AlignmentStakeholdersStrategyFacilitation |