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 ExampleRAID LogFailure Mode and Effects AnalysisAcceptance Criteria Workshop
| Criterion |  Agile Specification by Example |  Delivery RAID Log |  Operations Failure Mode and Effects Analysis |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
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. | 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 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. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 60-90 min pro Feature | 30 min Setup, dann laufend | 2-6 h | 20-40 min pro Story |
Participantsdifferent | 3-6 | 1-3 maintaining, briefing for everyone | 3-10 | 3-6 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | RAID Log, Status Report Source | FMEA Table, Risk Priority, Mitigation Actions | Acceptance Criteria, Story Update |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | RiskTrackingStakeholdersGovernance | RiskQualityOperationsRoot cause | AgileRequirementsRefinementBehavior-Driven Development |