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 Responsibility Poker |  Agile Sprint Retrospective |  Operations Accountability Ladder |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on. | 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 | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 20-45 min | 45-90 min |
Participantsdifferent | 3-10 | Scrum Team | 1-8 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Improvement actions, Team agreements | Ownership Reflection, Action Commitment, Coaching Notes | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RolesResponsibilityTeamFacilitation | RetrospectiveImprovementLearning | ResponsibilityLeadershipTeam | RetrospectiveImprovementExperimentsTeam |