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 4Ls Retrospective |  Operations 5 Whys |
|---|---|---|---|
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 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitysame | Low | Low | Low |
Timedifferent | 30 min Setup, dann laufend | 45–75 min | 15-30 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Team members involved | 2-6 |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | 4Ls Board, Learning Themes, Improvement Actions | Root cause notes, Countermeasures |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RetrospectiveLearningReflectionTeam | Root causeIncidentLeanProblem solving |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
