View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Cost of Delay |  Agile 4Ls Retrospective |  Agile Start Stop Continue |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | 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. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | 90-180 min | 45–75 min | 30-60 min | 45-90 min |
Participantsdifferent | 3-8 | Team members involved | 3-12 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | CoD Table, Prioritization Sequence | 4Ls Board, Learning Themes, Improvement Actions | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | PrioritizationDeliveryEconomicsDecision | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam |