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 Three Amigos |  Operations Failure Mode and Effects Analysis |  Agile Specification by Example |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Low | High | Medium |
Timedifferent | 15-30 min | 2-6 h | 60-90 min pro Feature |
Participantsdifferent | 3 | 3-10 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Clarified Story, Test Examples, Open Questions | FMEA Table, Risk Priority, Mitigation Actions | Example Table, Acceptance Tests |
Tagsno overlap | CollaborationBehavior-Driven DevelopmentQualityRefinement | RiskQualityOperationsRoot cause | AgileRequirementsExamplesBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
