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 Fault Tree Analysis |  Agile Example Mapping |  Agile Three Amigos |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 | High | Low | Low | High |
Timedifferent | 2-6 h | 30-60 min | 15-30 min | 2-6 h |
Participantsdifferent | 3-8 | 3-7 | 3 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Example Map, Acceptance Criteria, Open Questions | Clarified Story, Test Examples, Open Questions | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | RiskRoot causeSafety | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CollaborationBehavior-Driven DevelopmentQualityRefinement | RiskQualityOperationsRoot cause |