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 |  Operations Failure Mode and Effects Analysis |  Agile Example Mapping |
|---|---|---|---|---|
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 carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 60-90 min pro Feature | 30 min Setup, dann laufend | 2-6 h | 30-60 min |
Participantsdifferent | 3-6 | 1-3 maintaining, briefing for everyone | 3-10 | 3-7 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | RAID Log, Status Report Source | FMEA Table, Risk Priority, Mitigation Actions | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | RiskTrackingStakeholdersGovernance | RiskQualityOperationsRoot cause | Behavior-Driven DevelopmentRequirementsExamplesRefinement |