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 |  Facilitation Responsibility Poker |  Agile Sprint Retrospective |  Agile 4Ls 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 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 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 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | Halber Tag bis 2 Tage | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45–75 min |
Participantsdifferent | 15-200 | 3-10 | Scrum Team | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Session Board, Session Notes, Community Learnings | Responsibility Map, Role Agreements, Open Questions | Improvement actions, Team agreements | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | FacilitationLarge groupLearning | RolesResponsibilityTeamFacilitation | RetrospectiveImprovementLearning | RetrospectiveLearningReflectionTeam |