View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Team Charter |  Team Design Team Topologies Interaction Modes |  Agile 4Ls Retrospective |  Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | 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 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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 2-4 h | Half day | 45–75 min | 30-60 min |
Participantsdifferent | 3-12 | Team-Leads plus Architecture | Team members involved | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | Interaction Heat Map, Agreements per Pair | 4Ls Board, Learning Themes, Improvement Actions | Start Stop Continue Board, Improvement Actions |
Tags1 shared | TeamAlignmentCollaboration | TeamAlignmentCollaborationOrganization | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementTeamReflection |