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 |  Team Design Team Topologies Interaction Modes |  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 several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30-60 min | Half day | 45–75 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 3-12 | Team-Leads plus Architecture | Team members involved | Scrum Team |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Interaction Heat Map, Agreements per Pair | 4Ls Board, Learning Themes, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | RetrospectiveImprovementTeamReflection | TeamAlignmentCollaborationOrganization | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementLearning |