View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Time Blocking |  Agile Start Stop Continue |  Agile Starfish Retrospective |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure. | 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 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-30 min Planung, laufend | 30-60 min | 45-90 min | 45–75 min |
Participantsdifferent | 1 | 3-12 | 4-12 | Team members involved |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | Blocked Calendar, Capacity View, Focus Plan | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | PlanningTime managementFocus | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |