View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Team Charter | ![]() Agile 4Ls Retrospective | ![]() Agile Start Stop Continue | ![]() Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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 deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 2-4 h | 45–75 min | 30-60 min | 45-90 min |
Participantsdifferent | 3-12 | Team members involved | 3-12 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | 4Ls Board, Learning Themes, Improvement Actions | Start Stop Continue Board, Improvement Actions | Sailboat Board, Risks, Improvement Actions |
Tags1 shared | TeamAlignmentCollaboration | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementTeamReflection | RetrospectiveTeamImprovement |



