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 |  Delivery RAID Log |  Architecture Architecture Decision Record |  Agile ROAM Board |
|---|---|---|---|---|
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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-60 min | 30 min Setup, dann laufend | 15-45 min | 20-40 min initial, dann laufend |
Participantsdifferent | 2-9 | 1-3 maintaining, briefing for everyone | 1-3 | 3-15 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Ideal Day Estimates, Assumption Notes, Capacity Caveats | RAID Log, Status Report Source | ADR File, Decision Log, Rationale | ROAM Board, Owner List |
Tagsno overlap | EstimationEffortAgile | RiskTrackingStakeholdersGovernance | ArchitectureRationaleDocumentationGovernance | RiskAgileTrackingAlignment |