View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Fishbone Diagram |  Agile Specification by Example |  Agile Three Amigos |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | 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 story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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 | Low | Medium | Low | High |
Timedifferent | 30-60 min | 60-90 min pro Feature | 15-30 min | 2-6 h |
Participantsdifferent | 2-8 | 3-6 | 3 | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Fishbone Diagram, Cause Categories, Investigation Backlog | Example Table, Acceptance Tests | Clarified Story, Test Examples, Open Questions | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | Root causeQualityOperations | AgileRequirementsExamplesBehavior-Driven Development | CollaborationBehavior-Driven DevelopmentQualityRefinement | RiskQualityOperationsRoot cause |