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 Shape Up |  Operations Time Blocking |  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. | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. | With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure. | 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 | Medium | Low | High |
Timedifferent | Ongoing | 6 Wochen Cycle + 2 Wochen Cool-Down | 15-30 min Planung, laufend | 30-90 min Setup, danach laufend |
Participantsdifferent | 2-12 | 2-4 pro Pitch | 1 | 1-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Blocked Calendar, Capacity View, Focus Plan | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | FlowVisual managementDelivery | PlanningDeliveryAutonomy | PlanningTime managementFocus | ForecastingFlowDelivery |