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 Value Stream Mapping |  Operations Waste Analysis |  Agile 4Ls Retrospective |  Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 45-120 min | 45–75 min | 30-60 min |
Participantsdifferent | 4-10 | 2-8 | Team members involved | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Waste Map, Prioritized Waste, Improvement Backlog | 4Ls Board, Learning Themes, Improvement Actions | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | LeanFlowWasteDelivery | WasteLeanProcess improvement | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementTeamReflection |