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 Sailboat Retrospective |  Facilitation Responsibility Poker |  Agile Sprint Retrospective |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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-90 min | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-90 min |
Participantsdifferent | 4-12 | 3-10 | Scrum Team | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Responsibility Map, Role Agreements, Open Questions | Improvement actions, Team agreements | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveTeamImprovement | RolesResponsibilityTeamFacilitation | RetrospectiveImprovementLearning | RetrospectiveImprovementExperimentsTeam |