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 4Ls Retrospective |  Knowledge Modeling Teach-back |  Team Design Team API |
|---|---|---|---|
Purposedifferent | 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. | Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations. | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. |
Complexitysame | Low | Low | Low |
Timedifferent | 45–75 min | 5-20 min | Half day initial, dann laufend |
Participantsdifferent | Team members involved | 2-8 | Ein Team plus Stakeholder |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Understanding Check, Clarification Notes, Learning Gaps | Team API Document |
Tagsno overlap | RetrospectiveLearningReflectionTeam | LearningUnderstandingCommunication | TeamAlignmentCommunicationService |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
