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 Competency Questions |  Knowledge Modeling Shape-First Modeling |
|---|---|---|---|
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. | 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. | Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 20-40 min pro Story | 2-4 h | Halber Tag pro Domain Slice |
Participantsdifferent | 3-6 | 2-8 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Acceptance Criteria, Story Update | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | OntologyKnowledge graphScopeRequirementsSemantic | Knowledge graphValidationSemantic |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
