View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Competency Questions |  Agile Acceptance Criteria Workshop |  Agile Specification by Example |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Medium | Low | Medium |
Timedifferent | 2-4 h | 20-40 min pro Story | 60-90 min pro Feature |
Participantsdifferent | 2-8 | 3-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Acceptance Criteria, Story Update | Example Table, Acceptance Tests |
Tags1 shared | OntologyKnowledge graphScopeRequirementsSemantic | AgileRequirementsRefinementBehavior-Driven Development | AgileRequirementsExamplesBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
