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 4Ls Retrospective | ![]() Decision Making Delphi Method | ![]() Agile Start Stop Continue | ![]() Agile Sprint Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | 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 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 | Low | High | Low | Low |
Timedifferent | 45–75 min | 1-4 Wochen | 30-60 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | Team members involved | 6-30 Experten | 3-12 | Scrum Team |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Expert Forecast, Consensus Range, Assumption Notes | Start Stop Continue Board, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | RetrospectiveLearningReflectionTeam | ForecastingExpertsDecisionStrategy | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementLearning |



