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 Scrum |  Knowledge Modeling Linked Open Terms |  Knowledge Modeling Competency Questions |  Knowledge Modeling Property Graph Schema Design |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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. | Property Graph Schema Design turns business and technical requirements into a robust graph schema. It fits when query patterns, constraints, and migrations need to be thought about together. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | Wochen bis Monate | 2-4 h | 4-8 h initial, dann iterativ |
Participantsdifferent | 3-10 (Scrum Team) | 2-8 | 2-8 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries |
Tagsno overlap | AgileIterationCadence | OntologyMethodologyAgileSemantic | OntologyKnowledge graphScopeRequirementsSemantic | Knowledge graphModelingSemantic |