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 Responsibility Poker |  Facilitation Barcamp |  Agile Sailboat Retrospective |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | Halber Tag bis 2 Tage | 45-90 min | 45-90 min |
Participantsdifferent | 3-10 | 15-200 | 4-12 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Session Board, Session Notes, Community Learnings | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RolesResponsibilityTeamFacilitation | FacilitationLarge groupLearning | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam |