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 |  Agile ROAM Board |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-60 min | 30 min Setup, dann laufend | 20-40 min initial, dann laufend | 20-40 min pro Story |
Participantsdifferent | 3-7 | 1-3 maintaining, briefing for everyone | 3-15 | 3-6 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | RAID Log, Status Report Source | ROAM Board, Owner List | Acceptance Criteria, Story Update |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment | AgileRequirementsRefinementBehavior-Driven Development |