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 RAID Log | ![]() Delivery Monte Carlo Forecasting | ![]() Facilitation Dot Estimation | ![]() Delivery Communication Plan |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 30 min Setup, dann laufend | 30-90 min Setup, danach laufend | 5-20 min | 45-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-8 | 3-20 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Forecast Percentiles, Throughput Dataset, Risk Communication | Effort Heatmap, Risk Signals, Discussion Targets | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ForecastingFlowDelivery | EstimationEffortRisk | CommunicationStakeholdersDeliveryPlanning |



