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 Scrum |  Agile Starfish Retrospective |  Agile Sailboat Retrospective |
|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 45-90 min | 45-90 min |
Participantsdifferent | 3-10 (Scrum Team) | 4-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Starfish Board, Practice Changes, Experiments | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | AgileIterationCadence | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
