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 Starfish Retrospective |  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 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 | Medium | Low |
Timedifferent | 45-90 min | Half day | 45–75 min |
Participantsdifferent | 4-12 | Team-Leads plus Architecture | Team members involved |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Interaction Heat Map, Agreements per Pair | 4Ls Board, Learning Themes, Improvement Actions |
Tags1 shared | RetrospectiveImprovementExperimentsTeam | TeamAlignmentCollaborationOrganization | RetrospectiveLearningReflectionTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
