View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile NoEstimates |  Delivery RAID Log |  Facilitation Stakeholder Salience Model |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | laufend | 30 min Setup, dann laufend | 60-90 min | 1-2 h |
Participantsdifferent | 2-12 | 1-3 maintaining, briefing for everyone | 3-6 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Throughput Data, Flow Forecast, Slicing Rules | RAID Log, Status Report Source | Salience Diagram, Strategy per Class | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | EstimationForecastingFlow | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance | AlignmentStakeholdersStrategyFacilitation |