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