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 Start Stop Continue |  Knowledge Modeling Peer Instruction |  Agile 4Ls Retrospective |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | Peer Instruction uses group thinking to clarify difficult terms or concepts faster. The method combines individual reflection with social correction and shared precision. | 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 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30-60 min | 10-20 min je Frage | 45–75 min | 45-90 min |
Participantsdifferent | 3-12 | 6-50 | Team members involved | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Concept Questions, Vote Results, Learning Notes | 4Ls Board, Learning Themes, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveImprovementTeamReflection | LearningDialogueFacilitation | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementExperimentsTeam |