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 Sprint Retrospective | ![]() Agile Start Stop Continue | ![]() Facilitation Barcamp | ![]() Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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 | Low | Medium | Low |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 30-60 min | Halber Tag bis 2 Tage | 45-90 min |
Participantsdifferent | Scrum Team | 3-12 | 15-200 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Improvement actions, Team agreements | Start Stop Continue Board, Improvement Actions | Session Board, Session Notes, Community Learnings | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveImprovementLearning | RetrospectiveImprovementTeamReflection | FacilitationLarge groupLearning | RetrospectiveImprovementExperimentsTeam |



