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 Start Stop Continue |  Delivery RAID Log |  Agile Starfish Retrospective |  Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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-60 min | 30 min Setup, dann laufend | 45-90 min | 45-90 min |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 4-12 | 4-12 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | RAID Log, Status Report Source | Starfish Board, Practice Changes, Experiments | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementTeamReflection | RiskTrackingStakeholdersGovernance | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamImprovement |