View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Competency QuestionsSpecification by ExampleFailure Mode and Effects AnalysisAcceptance Criteria Workshop
| Criterion |  Knowledge Modeling Competency Questions |  Agile Specification by Example |  Operations Failure Mode and Effects Analysis |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
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 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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 | Medium | Medium | High | Low |
Timedifferent | 2-4 h | 60-90 min pro Feature | 2-6 h | 20-40 min pro Story |
Participantsdifferent | 2-8 | 3-6 | 3-10 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Example Table, Acceptance Tests | FMEA Table, Risk Priority, Mitigation Actions | Acceptance Criteria, Story Update |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | AgileRequirementsExamplesBehavior-Driven Development | RiskQualityOperationsRoot cause | AgileRequirementsRefinementBehavior-Driven Development |