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 Start Stop Continue | ![]() Agile 4Ls Retrospective | ![]() Agile Starfish 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 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 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 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 2-4 h | 30-60 min | 45–75 min | 45-90 min |
Participantsdifferent | 3-12 | 3-12 | Team members involved | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | Start Stop Continue Board, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tags1 shared | TeamAlignmentCollaboration | RetrospectiveImprovementTeamReflection | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementExperimentsTeam |



