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 |  Operations Learning Review |  Operations Failure Mode and Effects Analysis |  Agile 4Ls 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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 30-60 min | 1-3 h | 2-6 h | 45–75 min |
Participantsdifferent | 3-12 | 3-10 | 3-10 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions | FMEA Table, Risk Priority, Mitigation Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementTeamReflection | LearningRetrospectiveIncidentOperations | RiskQualityOperationsRoot cause | RetrospectiveLearningReflectionTeam |