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 Start Stop Continue |  Innovation TRIZ |  Agile 4Ls Retrospective |  Agile Sprint Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | For technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. | 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 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 | 30-60 min | 1-4 h | 45–75 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 3-12 | 2-8 | Team members involved | Scrum Team |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Contradiction Statement, Inventive Principles, Solution Concepts | 4Ls Board, Learning Themes, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | RetrospectiveImprovementTeamReflection | InnovationProblem solvingContradictionsCreativity | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementLearning |