View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery Shape Up | ![]() Product Strategy Lean Canvas | ![]() Delivery Value Stream Mapping | ![]() Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
Purposedifferent | 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. | When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. | 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. | 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 | Medium | High |
Timedifferent | 6 Wochen Cycle + 2 Wochen Cool-Down | 45-90 min | 1-3 h | 30-90 min Setup, danach laufend |
Participantsdifferent | 2-4 pro Pitch | 1-6 | 4-10 | 1-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Lean Canvas, Core Assumptions, Experiment Backlog | Current-state map, Future-state map, Bottleneck list | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | PlanningDeliveryAutonomy | StartupLeanAssumptionsBusiness model | LeanFlowWasteDelivery | ForecastingFlowDelivery |



