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 NeOn Methodology |  Agile Example Mapping |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 60-90 min pro Feature | Mehrere Wochen bis Monate | 30-60 min |
Participantsdifferent | 3-10 (Scrum Team) | 3-6 | 2-10 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Table, Acceptance Tests | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileIterationCadence | AgileRequirementsExamplesBehavior-Driven Development | OntologyMethodologyReuseSemanticEngineering | Behavior-Driven DevelopmentRequirementsExamplesRefinement |