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 |  Agile Starfish Retrospective |  Agile Sprint Retrospective |  Agile Start Stop Continue |
|---|---|---|---|---|
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 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 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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 5-20 min | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 30-60 min |
Participantsdifferent | 2-8 | 4-12 | Scrum Team | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Understanding Check, Clarification Notes, Learning Gaps | Starfish Board, Practice Changes, Experiments | Improvement actions, Team agreements | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | LearningUnderstandingCommunication | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementLearning | RetrospectiveImprovementTeamReflection |