View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Starfish RetrospectiveStart Stop ContinueTeam Topologies Interaction Modes4Ls Retrospective
| Criterion |  Agile Starfish Retrospective |  Agile Start Stop Continue |  Team Design Team Topologies Interaction Modes |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45-90 min | 30-60 min | Half day | 45–75 min |
Participantsdifferent | 4-12 | 3-12 | Team-Leads plus Architecture | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions | Interaction Heat Map, Agreements per Pair | 4Ls Board, Learning Themes, Improvement Actions |
Tags1 shared | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection | TeamAlignmentCollaborationOrganization | RetrospectiveLearningReflectionTeam |