View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Barcamp |  Agile Sailboat Retrospective |  Agile Starfish Retrospective |  Agile Sprint Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | Halber Tag bis 2 Tage | 45-90 min | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 15-200 | 4-12 | 4-12 | Scrum Team |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Session Board, Session Notes, Community Learnings | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments | Improvement actions, Team agreements |
Tagsno overlap | FacilitationLarge groupLearning | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementLearning |