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 |  Agile ROAM Board |  Agile 4Ls Retrospective |  Agile Sprint 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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-60 min | 20-40 min initial, dann laufend | 45–75 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 3-12 | 3-15 | Team members involved | Scrum Team |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | ROAM Board, Owner List | 4Ls Board, Learning Themes, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | RetrospectiveImprovementTeamReflection | RiskAgileTrackingAlignment | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementLearning |