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 Sprint Retrospective |  Agile Starfish 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 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 |
Timedifferent | Half day initial, dann laufend | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-90 min |
Participantsdifferent | Ein Team plus Stakeholder | Scrum Team | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Team API Document | Improvement actions, Team agreements | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | TeamAlignmentCommunicationService | RetrospectiveImprovementLearning | RetrospectiveImprovementExperimentsTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
