View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Specification by ExampleFailure Mode and Effects AnalysisCompetency QuestionsFishbone Diagram
| Criterion |  Agile Specification by Example |  Operations Failure Mode and Effects Analysis |  Knowledge Modeling Competency Questions |  Operations Fishbone Diagram |
|---|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 60-90 min pro Feature | 2-6 h | 2-4 h | 30-60 min |
Participantsdifferent | 3-6 | 3-10 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | FMEA Table, Risk Priority, Mitigation Actions | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | RiskQualityOperationsRoot cause | OntologyKnowledge graphScopeRequirementsSemantic | Root causeQualityOperations |