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