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 |  Agile Start Stop Continue |
|---|---|---|---|---|
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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45–75 min | 45-90 min | 45-90 min | 30-60 min |
Participantsdifferent | Team members involved | 3-10 | 3-10 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Responsibility Map, Role Agreements, Open Questions | Delegation Board, Decision Boundaries, Role Agreements | Start Stop Continue Board, Improvement Actions |
Tags1 shared | RetrospectiveLearningReflectionTeam | RolesResponsibilityTeamFacilitation | AutonomyRolesTeam | RetrospectiveImprovementTeamReflection |