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 Scrum |  Delivery RAID Log |  Architecture arc42 |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 30 min Setup, dann laufend | 1-2 Tage | 20-40 min initial, dann laufend |
Participantsdifferent | 3-10 (Scrum Team) | 1-3 maintaining, briefing for everyone | 1-4 | 3-15 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | RAID Log, Status Report Source | Architecture Document, Context View, Runtime View, Deployment View | ROAM Board, Owner List |
Tagsno overlap | AgileIterationCadence | RiskTrackingStakeholdersGovernance | ArchitectureDocumentationCommunication | RiskAgileTrackingAlignment |