View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Failure Mode and Effects AnalysisFishbone DiagramSpecification by ExampleAcceptance Criteria Workshop
| Criterion |  Operations Failure Mode and Effects Analysis |  Operations Fishbone Diagram |  Agile Specification by Example |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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 | High | Low | Medium | Low |
Timedifferent | 2-6 h | 30-60 min | 60-90 min pro Feature | 20-40 min pro Story |
Participantsdifferent | 3-10 | 2-8 | 3-6 | 3-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | FMEA Table, Risk Priority, Mitigation Actions | Fishbone Diagram, Cause Categories, Investigation Backlog | Example Table, Acceptance Tests | Acceptance Criteria, Story Update |
Tagsno overlap | RiskQualityOperationsRoot cause | Root causeQualityOperations | AgileRequirementsExamplesBehavior-Driven Development | AgileRequirementsRefinementBehavior-Driven Development |