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 |  Agile NoEstimates |  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 a RAID Log and a source for status reporting. | 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. | 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 | Low | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | laufend | 60-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-12 | 3-6 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Throughput Data, Flow Forecast, Slicing Rules | Salience Diagram, Strategy per Class |
Tagsno overlap | RiskTrackingStakeholdersGovernance | EstimationForecastingFlow | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
