View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Agile ROAM Board |  DevOps Blameless Postmortem |
|---|---|---|---|
Purposedifferent | 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. | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 20-40 min initial, dann laufend | 30-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-15 | 3-12 |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | ROAM Board, Owner List | Postmortem Doc, Action Items, Timeline |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment | Site Reliability EngineeringIncidentLearningReliability |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
