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 ROAM Board |  Facilitation Stakeholder Salience Model |  Agile Ideal Days |  Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | 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. | 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 effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 20-40 min initial, dann laufend | 60-90 min | 15-60 min | 30 min Setup, dann laufend |
Participantsdifferent | 3-15 | 3-6 | 2-9 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | ROAM Board, Owner List | Salience Diagram, Strategy per Class | Ideal Day Estimates, Assumption Notes, Capacity Caveats | RAID Log, Status Report Source |
Tagsno overlap | RiskAgileTrackingAlignment | StakeholdersFacilitationAlignmentGovernance | EstimationEffortAgile | RiskTrackingStakeholdersGovernance |