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 Ideal Days |  Agile ROAM Board |  Facilitation Stakeholder Mapping |  Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | 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. | 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-60 min | 20-40 min initial, dann laufend | 60–90 min | 30 min Setup, dann laufend |
Participantsdifferent | 2-9 | 3-15 | 2-8 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Ideal Day Estimates, Assumption Notes, Capacity Caveats | ROAM Board, Owner List | Stakeholder Map, Engagement Plan, Risk Notes | RAID Log, Status Report Source |
Tagsno overlap | EstimationEffortAgile | RiskAgileTrackingAlignment | StakeholdersAlignmentFacilitationChange | RiskTrackingStakeholdersGovernance |