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 Shape-First Modeling |  Agile Acceptance Criteria Workshop |
|---|---|---|---|
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. | 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 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 30-60 min | Halber Tag pro Domain Slice | 20-40 min pro Story |
Participantsdifferent | 3-7 | 1-4 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Acceptance Criteria, Story Update |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Knowledge graphValidationSemantic | AgileRequirementsRefinementBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
