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 |  DevOps Incident Command |  DevOps Game Day |
|---|---|---|---|---|
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. | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | Ongoing | 1-3 h | As needed | Halber Tag |
Participantsdifferent | 2-12 | 4-10 | 4-15 | 5-20 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Current-state map, Future-state map, Bottleneck list | Incident Log, Action Tracker, Stakeholder Updates | Simulation Notes, Gaps List, Updated Runbooks |
Tagsno overlap | FlowVisual managementDelivery | LeanFlowWasteDelivery | IncidentOperationsReliability | ResilienceOperationsIncident |