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 |  DevOps Blameless Postmortem |  Agile Start Stop Continue |  Agile 4Ls Retrospective |
|---|---|---|---|---|
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. | 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. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30 min Setup, dann laufend | 30-90 min | 30-60 min | 45–75 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-12 | 3-12 | Team members involved |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | Postmortem Doc, Action Items, Timeline | Start Stop Continue Board, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Site Reliability EngineeringIncidentLearningReliability | RetrospectiveImprovementTeamReflection | RetrospectiveLearningReflectionTeam |