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 |  Agile Specification by Example |  Knowledge Modeling Competency Questions |  Knowledge Modeling Linked Open Terms |
|---|---|---|---|---|
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. | 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. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 60-90 min pro Feature | 2-4 h | Wochen bis Monate |
Participantsdifferent | 3-10 (Scrum Team) | 3-6 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Table, Acceptance Tests | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan |
Tagsno overlap | AgileIterationCadence | AgileRequirementsExamplesBehavior-Driven Development | OntologyKnowledge graphScopeRequirementsSemantic | OntologyMethodologyAgileSemantic |