View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Agile Starfish Retrospective |  Agile Sailboat Retrospective |
|---|---|---|---|
Purposedifferent | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | Half day initial, dann laufend | 45-90 min | 45-90 min |
Participantsdifferent | Ein Team plus Stakeholder | 4-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Team API Document | Starfish Board, Practice Changes, Experiments | Sailboat Board, Risks, Improvement Actions |
Tags1 shared | TeamAlignmentCommunicationService | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
