View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:RAID LogFailure Mode and Effects AnalysisAcceptance Criteria WorkshopSpecification by Example
| Criterion |  Delivery RAID Log |  Operations Failure Mode and Effects Analysis |  Agile Acceptance Criteria Workshop |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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. | 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 | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 2-6 h | 20-40 min pro Story | 60-90 min pro Feature |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-10 | 3-6 | 3-6 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | FMEA Table, Risk Priority, Mitigation Actions | Acceptance Criteria, Story Update | Example Table, Acceptance Tests |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RiskQualityOperationsRoot cause | AgileRequirementsRefinementBehavior-Driven Development | AgileRequirementsExamplesBehavior-Driven Development |