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 Communication Plan |  Agile 4Ls 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. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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 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 | 45-90 min | 45–75 min | 45-90 min |
Participantsdifferent | 3-12 | 2-6 | Team members involved | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Communication Plan, Channel Matrix, Message Cadence | 4Ls Board, Learning Themes, Improvement Actions | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementTeamReflection | CommunicationStakeholdersDeliveryPlanning | RetrospectiveLearningReflectionTeam | RetrospectiveTeamImprovement |