View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Specification by Example |  Product Strategy ICE Scoring |  Delivery MoSCoW |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | When ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 60-90 min pro Feature | 30-60 min | 30-90 min | 2-4 h |
Participantsdifferent | 3-6 | 2-8 | 3-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | ICE Table, Top Idea List | Prioritized Backlog, Release Scope, Tradeoff Notes | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | PrioritizationScoringGrowthDecision | PrioritizationScopeDecision | OntologyKnowledge graphScopeRequirementsSemantic |