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 Expectation Mapping |  Agile Start Stop Continue |
|---|---|---|---|---|
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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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-90 min | 45–75 min | 45-90 min | 30-60 min |
Participantsdifferent | 3-10 | Team members involved | 3-12 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | 4Ls Board, Learning Themes, Improvement Actions | Expectation Map, Alignment Notes, Agreements | Start Stop Continue Board, Improvement Actions |
Tags1 shared | AutonomyRolesTeam | RetrospectiveLearningReflectionTeam | AlignmentStakeholdersTeam | RetrospectiveImprovementTeamReflection |