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 Example Mapping |  Decision Making OODA Loop |  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 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. | In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia. | 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 | Medium |
Timedifferent | 2-4 h | 30-60 min | 15-60 min je Zyklus | 60-90 min pro Feature |
Participantsdifferent | 2-8 | 3-7 | 1-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Example Map, Acceptance Criteria, Open Questions | Situation Assessment, Decision Loop, Action Updates | Example Table, Acceptance Tests |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | Behavior-Driven DevelopmentRequirementsExamplesRefinement | DecisionChangeLearningStrategy | AgileRequirementsExamplesBehavior-Driven Development |