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 |  Agile Sailboat Retrospective |  Facilitation Delegation Poker |  Agile 4Ls 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 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 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 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 45-90 min | 45-90 min | 45–75 min |
Participantsdifferent | 3-10 | 4-12 | 3-10 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Sailboat Board, Risks, Improvement Actions | Delegation Board, Decision Boundaries, Role Agreements | 4Ls Board, Learning Themes, Improvement Actions |
Tags1 shared | RolesResponsibilityTeamFacilitation | RetrospectiveTeamImprovement | AutonomyRolesTeam | RetrospectiveLearningReflectionTeam |