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 ROAM Board | ![]() Delivery RAID Log | ![]() Agile Example Mapping | ![]() Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | 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 | 20-40 min initial, dann laufend | 30 min Setup, dann laufend | 30-60 min | 20-40 min pro Story |
Participantsdifferent | 3-15 | 1-3 maintaining, briefing for everyone | 3-7 | 3-6 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | ROAM Board, Owner List | RAID Log, Status Report Source | Example Map, Acceptance Criteria, Open Questions | Acceptance Criteria, Story Update |
Tagsno overlap | RiskAgileTrackingAlignment | RiskTrackingStakeholdersGovernance | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsRefinementBehavior-Driven Development |



