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 Example Mapping |  Knowledge Modeling Competency Questions |  Knowledge Modeling Shape-First Modeling |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Medium |
Timedifferent | 30-60 min | 2-4 h | Halber Tag pro Domain Slice | 60-90 min pro Feature |
Participantsdifferent | 3-7 | 2-8 | 1-4 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Example Table, Acceptance Tests |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | OntologyKnowledge graphScopeRequirementsSemantic | Knowledge graphValidationSemantic | AgileRequirementsExamplesBehavior-Driven Development |