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 |  Delivery RAID Log |  Agile Three Amigos |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | Medium | Low | Low | High |
Timedifferent | 60-90 min pro Feature | 30 min Setup, dann laufend | 15-30 min | 2-6 h |
Participantsdifferent | 3-6 | 1-3 maintaining, briefing for everyone | 3 | 3-10 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | RAID Log, Status Report Source | Clarified Story, Test Examples, Open Questions | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | RiskTrackingStakeholdersGovernance | CollaborationBehavior-Driven DevelopmentQualityRefinement | RiskQualityOperationsRoot cause |