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 | ![]() Agile Scrum | ![]() Knowledge Modeling NeOn Methodology | ![]() Knowledge Modeling Linked Open Terms |
|---|---|---|---|---|
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 a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | The NeOn Methodology structures ontology work as a controlled process with reuse, scenarios, and reviews. It is useful when ontologies should not emerge ad hoc but modularly and reusably. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 60-90 min pro Feature | 1-4 Wochen je Sprint, laufend | Mehrere Wochen bis Monate | Wochen bis Monate |
Participantsdifferent | 3-6 | 3-10 (Scrum Team) | 2-10 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | AgileIterationCadence | OntologyMethodologyReuseSemanticEngineering | OntologyMethodologyAgileSemantic |



