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 |  Facilitation Open Space Technology |  Agile Sprint Retrospective |  Agile 4Ls 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 a complex topic does not yet have a fitting agenda, Open Space Technology hands topic ownership back to the participants. The format suits questions that only move forward when real interest determines the order. | 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 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. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 30-60 min | 0.5-2 Tage | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45–75 min |
Participantsdifferent | 3-12 | 20-500+ | Scrum Team | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Session Marketplace, Proceedings, Action Topics | Improvement actions, Team agreements | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementTeamReflection | FacilitationLarge groupAutonomy | RetrospectiveImprovementLearning | RetrospectiveLearningReflectionTeam |