View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile 4Ls Retrospective |  Delivery RAID Log |  Agile Starfish Retrospective |
|---|---|---|---|
Purposedifferent | 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. | 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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitysame | Low | Low | Low |
Timedifferent | 45–75 min | 30 min Setup, dann laufend | 45-90 min |
Participantsdifferent | Team members involved | 1-3 maintaining, briefing for everyone | 4-12 |
Formatdifferent | Workshop | Async | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | RAID Log, Status Report Source | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveLearningReflectionTeam | RiskTrackingStakeholdersGovernance | RetrospectiveImprovementExperimentsTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
