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 |  Delivery Value Stream Mapping |  Knowledge Modeling Feynman Technique |  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 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. | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | 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 | Medium | Low | Low |
Timedifferent | Ongoing | 1-3 h | 20-60 min | 45–75 min |
Participantsdifferent | 2-12 | 4-10 | 1 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Current-state map, Future-state map, Bottleneck list | Plain-language Explanation, Knowledge Gaps, Study Notes | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | FlowVisual managementDelivery | LeanFlowWasteDelivery | LearningKnowledgeUnderstanding | RetrospectiveLearningReflectionTeam |