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 Delegation Poker |  Agile Sailboat Retrospective |  Agile Starfish Retrospective |
|---|---|---|---|---|
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 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 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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45–75 min | 45-90 min | 45-90 min | 45-90 min |
Participantsdifferent | Team members involved | 3-10 | 4-12 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Delegation Board, Decision Boundaries, Role Agreements | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tags1 shared | RetrospectiveLearningReflectionTeam | AutonomyRolesTeam | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam |