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 Delegation Poker |  Agile 4Ls Retrospective |  Facilitation Alignment Mapping |  Facilitation Responsibility Poker |
|---|---|---|---|---|
Purposedifferent | 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45-90 min | 45–75 min | 1-2 h | 45-90 min |
Participantsdifferent | 3-10 | Team members involved | 4-12 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | 4Ls Board, Learning Themes, Improvement Actions | Alignment Map, Open Issues, Decision Questions | Responsibility Map, Role Agreements, Open Questions |
Tagsno overlap | AutonomyRolesTeam | RetrospectiveLearningReflectionTeam | AlignmentStakeholdersStrategyFacilitation | RolesResponsibilityTeamFacilitation |