View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Waste Analysis |  Delivery RAID Log |  Decision Making Three-Point Estimation |  Agile NoEstimates |
|---|---|---|---|---|
Purposedifferent | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | 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. | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes. | When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 45-120 min | 30 min Setup, dann laufend | 10-30 min je Item | laufend |
Participantsdifferent | 2-8 | 1-3 maintaining, briefing for everyone | 1-8 | 2-12 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | RAID Log, Status Report Source | Three-Point Estimate, Risk Range, Assumption Notes | Throughput Data, Flow Forecast, Slicing Rules |
Tagsno overlap | WasteLeanProcess improvement | RiskTrackingStakeholdersGovernance | EstimationUncertaintyForecasting | EstimationForecastingFlow |