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 |  Operations Fishbone Diagram |  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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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 | Low | Medium |
Timedifferent | 30-60 min | 2-4 h | 30-60 min | 60-90 min pro Feature |
Participantsdifferent | 3-7 | 2-8 | 2-8 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Fishbone Diagram, Cause Categories, Investigation Backlog | Example Table, Acceptance Tests |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | OntologyKnowledge graphScopeRequirementsSemantic | Root causeQualityOperations | AgileRequirementsExamplesBehavior-Driven Development |