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 Monte Carlo Forecasting |  Delivery RAID Log |  Engineering Kanban |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | High | Low | Medium | Medium |
Timedifferent | 30-90 min Setup, danach laufend | 30 min Setup, dann laufend | Ongoing | 60-90 min |
Participantsdifferent | 1-8 | 1-3 maintaining, briefing for everyone | 2-12 | 3-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | RAID Log, Status Report Source | Kanban board, WIP policies, Flow metrics | Salience Diagram, Strategy per Class |
Tagsno overlap | ForecastingFlowDelivery | RiskTrackingStakeholdersGovernance | FlowVisual managementDelivery | StakeholdersFacilitationAlignmentGovernance |