View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Agile Sprint Retrospective |  Agile 4Ls Retrospective |
|---|---|---|---|
Purposedifferent | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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. | 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 | Medium | Low | Low |
Timedifferent | Ongoing | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45–75 min |
Participantsdifferent | 2-12 | Scrum Team | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Improvement actions, Team agreements | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | FlowVisual managementDelivery | RetrospectiveImprovementLearning | RetrospectiveLearningReflectionTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
