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 | ![]() Decision Making Decision Rights Mapping | ![]() Facilitation Alignment Mapping |
|---|---|---|---|---|
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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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 | Low | Medium | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | laufend | 90-180 min | 1-2 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-12 | 4-12 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | Throughput Data, Flow Forecast, Slicing Rules | Decision Rights Matrix, Agreement | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | RiskTrackingStakeholdersGovernance | EstimationForecastingFlow | DecisionGovernanceAlignmentResponsibility | AlignmentStakeholdersStrategyFacilitation |



