View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Specification by ExampleAcceptance Criteria WorkshopFailure Mode and Effects AnalysisThree Amigos
| Criterion |  Agile Specification by Example |  Agile Acceptance Criteria Workshop |  Operations Failure Mode and Effects Analysis |  Agile Three Amigos |
|---|---|---|---|---|
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. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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 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. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 60-90 min pro Feature | 20-40 min pro Story | 2-6 h | 15-30 min |
Participantsdifferent | 3-6 | 3-6 | 3-10 | 3 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Acceptance Criteria, Story Update | FMEA Table, Risk Priority, Mitigation Actions | Clarified Story, Test Examples, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | AgileRequirementsRefinementBehavior-Driven Development | RiskQualityOperationsRoot cause | CollaborationBehavior-Driven DevelopmentQualityRefinement |