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 |  Operations After-Action Review |  Agile Sprint Retrospective |  Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | Ongoing | 20-45 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 30-90 min Setup, danach laufend |
Participantsdifferent | 2-12 | 3-12 | Scrum Team | 1-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Lessons learned, Action items, Event summary | Improvement actions, Team agreements | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | FlowVisual managementDelivery | LearningOperationsImprovement | RetrospectiveImprovementLearning | ForecastingFlowDelivery |