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 |  Agile Sprint Retrospective |  Agile Sailboat 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. | 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. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30 min Setup, dann laufend | 45–75 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Team members involved | Scrum Team | 4-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | 4Ls Board, Learning Themes, Improvement Actions | Improvement actions, Team agreements | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementLearning | RetrospectiveTeamImprovement |