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 Sailboat Retrospective |  Product Discovery Assumption Mapping |  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. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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 | Low | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 45-90 min | 45-60 min | 45–75 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 4-12 | 2-8 | Team members involved |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Sailboat Board, Risks, Improvement Actions | Assumption map, Test backlog, Risk ranking | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RetrospectiveTeamImprovement | AssumptionsRiskExperimentsValidation | RetrospectiveLearningReflectionTeam |