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 Barrier Analysis |  Agile 4Ls Retrospective |  Operations MORT Analysis |
|---|---|---|---|---|
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 a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. | 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. | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 30-60 min | 2-4 h | 45–75 min | Mehrere Tage bis Wochen |
Participantsdifferent | 3-12 | 2-6 | Team members involved | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | 4Ls Board, Learning Themes, Improvement Actions | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | RetrospectiveImprovementTeamReflection | Root causeSafetyIncident | RetrospectiveLearningReflectionTeam | Root causeSafetySystemicIncident |