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 |  Agile Sprint Retrospective |  Team Design Team Cognitive Load Assessment |
|---|---|---|---|
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 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 a team juggles too many domains, systems, or handoffs, it measures mental overload as an organizational problem. It clarifies responsibility, interaction, and load between teams. The result is captured as a cognitive-load profile and action list. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 60-90 min |
Participantsdifferent | 4-12 | Scrum Team | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Improvement actions, Team agreements | Cognitive Load Profile, Action List |
Tags1 shared | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementLearning | TeamComplexityImprovementDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
