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 Specification by Example |  Operations Fishbone Diagram |  Operations Kepner-Tregoe |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
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. | 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. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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. |
Complexitydifferent | Medium | Low | High | High |
Timedifferent | 60-90 min pro Feature | 30-60 min | 2-8 h | 2-6 h |
Participantsdifferent | 3-6 | 2-8 | 2-8 | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Fishbone Diagram, Cause Categories, Investigation Backlog | Problem Analysis, Decision Analysis, Risk Plan | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Root causeQualityOperations | Problem solvingRoot causeDecisionOperations | RiskQualityOperationsRoot cause |