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 Linked Open Terms | ![]() Knowledge Modeling Competency Questions | ![]() Product Strategy DIBB | ![]() Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | 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. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | Wochen bis Monate | 2-4 h | 1-2 h | 20-40 min pro Story |
Participantsdifferent | 2-8 | 2-8 | 2-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | DIBB document, Belief list, Bet list, Learning report | Acceptance Criteria, Story Update |
Tagsno overlap | OntologyMethodologyAgileSemantic | OntologyKnowledge graphScopeRequirementsSemantic | StrategyDecisionAssumptionsHypothesis | AgileRequirementsRefinementBehavior-Driven Development |



