View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Golden Path |  Agile Start Stop Continue |  Agile Starfish Retrospective |  Agile Sprint Retrospective |
|---|---|---|---|---|
Purposedifferent | When teams need a reliable default path for frequent use, sprawl quickly emerges without any guiding logic. Golden Path bundles the preferred path so good practice becomes easy and deviation becomes deliberate. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 Tage Setup, laufend | 30-60 min | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 2-8 | 3-12 | 4-12 | Scrum Team |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Golden Path Guide, Templates, Quality Checks | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments | Improvement actions, Team agreements |
Tagsno overlap | EngineeringProductivityGovernance | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementLearning |