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 Starfish Retrospective |  Agile Sailboat Retrospective |  Facilitation Responsibility Poker |  Facilitation Delegation Poker |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. |
Complexitysame | Low | Low | Low | Low |
Timesame | 45-90 min | 45-90 min | 45-90 min | 45-90 min |
Participantsdifferent | 4-12 | 4-12 | 3-10 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Sailboat Board, Risks, Improvement Actions | Responsibility Map, Role Agreements, Open Questions | Delegation Board, Decision Boundaries, Role Agreements |
Tags1 shared | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamImprovement | RolesResponsibilityTeamFacilitation | AutonomyRolesTeam |