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 Example Mapping | ![]() Knowledge Modeling Linked Open Terms | ![]() Knowledge Modeling NeOn Methodology |
|---|---|---|---|---|
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 a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | 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. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 1-4 Wochen je Sprint, laufend | 30-60 min | Wochen bis Monate | Mehrere Wochen bis Monate |
Participantsdifferent | 3-10 (Scrum Team) | 3-7 | 2-8 | 2-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Map, Acceptance Criteria, Open Questions | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | AgileIterationCadence | Behavior-Driven DevelopmentRequirementsExamplesRefinement | OntologyMethodologyAgileSemantic | OntologyMethodologyReuseSemanticEngineering |



