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 Acceptance Criteria Workshop |  Knowledge Modeling Linked Open Terms |  Agile Specification by Example |
|---|---|---|---|
Purposedifferent | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 20-40 min pro Story | Wochen bis Monate | 60-90 min pro Feature |
Participantsdifferent | 3-6 | 2-8 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Acceptance Criteria, Story Update | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Example Table, Acceptance Tests |
Tags1 shared | AgileRequirementsRefinementBehavior-Driven Development | OntologyMethodologyAgileSemantic | AgileRequirementsExamplesBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
