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 Example Mapping |  Delivery RAID Log |  Operations Fishbone Diagram |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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. | 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 a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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 | Low | Low | Medium |
Timedifferent | 30-60 min | 30 min Setup, dann laufend | 30-60 min | 60-90 min pro Feature |
Participantsdifferent | 3-7 | 1-3 maintaining, briefing for everyone | 2-8 | 3-6 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | RAID Log, Status Report Source | Fishbone Diagram, Cause Categories, Investigation Backlog | Example Table, Acceptance Tests |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RiskTrackingStakeholdersGovernance | Root causeQualityOperations | AgileRequirementsExamplesBehavior-Driven Development |