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 |  Facilitation Delegation Poker |  Agile Sprint Retrospective |
|---|---|---|---|
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 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 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 45-90 min | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 4-12 | 3-10 | Scrum Team |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Delegation Board, Decision Boundaries, Role Agreements | Improvement actions, Team agreements |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | AutonomyRolesTeam | RetrospectiveImprovementLearning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
