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 |  Agile Specification by Example |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | Wochen bis Monate | 60-90 min pro Feature | 2-4 h |
Participantsdifferent | 3-10 (Scrum Team) | 2-8 | 3-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Example Table, Acceptance Tests | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | AgileIterationCadence | OntologyMethodologyAgileSemantic | AgileRequirementsExamplesBehavior-Driven Development | OntologyKnowledge graphScopeRequirementsSemantic |