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 |  Agile Example Mapping |  Architecture Architecture Decision Record |  Delivery RAID Log |
|---|---|---|---|---|
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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 20-40 min initial, dann laufend | 30-60 min | 15-45 min | 30 min Setup, dann laufend |
Participantsdifferent | 3-15 | 3-7 | 1-3 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | ROAM Board, Owner List | Example Map, Acceptance Criteria, Open Questions | ADR File, Decision Log, Rationale | RAID Log, Status Report Source |
Tagsno overlap | RiskAgileTrackingAlignment | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance |