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 Sprint Retrospective |  Agile Start Stop Continue |  Agile Starfish 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 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 deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 | Low |
Timedifferent | 30 min Setup, dann laufend | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 30-60 min | 45-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Scrum Team | 3-12 | 4-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | Improvement actions, Team agreements | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RetrospectiveImprovementLearning | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam |