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 Specification by Example |  Operations Family Tree Analysis |  Agile Example Mapping |
|---|---|---|---|---|
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 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 series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. | 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. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | 2-6 h | 60-90 min pro Feature | 2-4 h | 30-60 min |
Participantsdifferent | 3-8 | 3-6 | 2-6 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Example Table, Acceptance Tests | Family Tree Diagram, Pattern Notes, Systemic Measures | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | RiskRoot causeSafety | AgileRequirementsExamplesBehavior-Driven Development | Root causePatternsIncidentSystemic | Behavior-Driven DevelopmentRequirementsExamplesRefinement |