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 |  Facilitation Alignment Mapping |  Delivery RAID Log |  Agile ROAM Board |
|---|---|---|---|---|
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. | 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. | 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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | laufend | 1-2 h | 30 min Setup, dann laufend | 20-40 min initial, dann laufend |
Participantsdifferent | 2-12 | 4-12 | 1-3 maintaining, briefing for everyone | 3-15 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Throughput Data, Flow Forecast, Slicing Rules | Alignment Map, Open Issues, Decision Questions | RAID Log, Status Report Source | ROAM Board, Owner List |
Tagsno overlap | EstimationForecastingFlow | AlignmentStakeholdersStrategyFacilitation | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment |