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 ROAM Board |  Agile Affinity Estimation |  Agile Planning Poker |
|---|---|---|---|---|
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 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 many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 20-40 min initial, dann laufend | 30-90 min | 2-5 min je Item |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-15 | 3-12 | 3-9 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | ROAM Board, Owner List | Affinity Size Map, Grouped Estimates, Unclear Items | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment | EstimationBacklogRelative sizing | EstimationAgileRelative sizingTeam |