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