View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team Topologies Interaction Modes |  Agile Starfish Retrospective |  Facilitation Team Charter |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 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 is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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 | Medium | Low | Medium | Low |
Timedifferent | Half day | 45-90 min | 2-4 h | 45–75 min |
Participantsdifferent | Team-Leads plus Architecture | 4-12 | 3-12 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | Starfish Board, Practice Changes, Experiments | Team Charter, Working Norms, Role Notes | 4Ls Board, Learning Themes, Improvement Actions |
Tags1 shared | TeamAlignmentCollaborationOrganization | RetrospectiveImprovementExperimentsTeam | TeamAlignmentCollaboration | RetrospectiveLearningReflectionTeam |