View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Fishbone Diagram | ![]() Knowledge Modeling Competency Questions | ![]() Agile Example Mapping | ![]() Agile Three Amigos |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30-60 min | 2-4 h | 30-60 min | 15-30 min |
Participantsdifferent | 2-8 | 2-8 | 3-7 | 3 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Fishbone Diagram, Cause Categories, Investigation Backlog | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Example Map, Acceptance Criteria, Open Questions | Clarified Story, Test Examples, Open Questions |
Tagsno overlap | Root causeQualityOperations | OntologyKnowledge graphScopeRequirementsSemantic | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CollaborationBehavior-Driven DevelopmentQualityRefinement |



