View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Teach-back |  Facilitation Barcamp |  Agile Sprint Retrospective |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 many people can contribute knowledge and the flow should stay open, Barcamp provides a framework for self-organized sessions. The format channels energy without defining the content too narrowly in advance. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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 | Low |
Timedifferent | 5-20 min | Halber Tag bis 2 Tage | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45–75 min |
Participantsdifferent | 2-8 | 15-200 | Scrum Team | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Understanding Check, Clarification Notes, Learning Gaps | Session Board, Session Notes, Community Learnings | Improvement actions, Team agreements | 4Ls Board, Learning Themes, Improvement Actions |
Tags1 shared | LearningUnderstandingCommunication | FacilitationLarge groupLearning | RetrospectiveImprovementLearning | RetrospectiveLearningReflectionTeam |