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 4Ls Retrospective |  Facilitation Responsibility Poker |  Facilitation Delegation Poker |  Facilitation Barcamp |
|---|---|---|---|---|
Purposedifferent | 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 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 decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45–75 min | 45-90 min | 45-90 min | Halber Tag bis 2 Tage |
Participantsdifferent | Team members involved | 3-10 | 3-10 | 15-200 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Responsibility Map, Role Agreements, Open Questions | Delegation Board, Decision Boundaries, Role Agreements | Session Board, Session Notes, Community Learnings |
Tagsno overlap | RetrospectiveLearningReflectionTeam | RolesResponsibilityTeamFacilitation | AutonomyRolesTeam | FacilitationLarge groupLearning |