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 |  Architecture Architecture Decision Record |  Agile Ideal Days |  Facilitation Dot Estimation |
|---|---|---|---|---|
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. | 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 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 size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30 min Setup, dann laufend | 15-45 min | 15-60 min | 5-20 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-3 | 2-9 | 3-20 |
Formatdifferent | Async | Async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | ADR File, Decision Log, Rationale | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Effort Heatmap, Risk Signals, Discussion Targets |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureRationaleDocumentationGovernance | EstimationEffortAgile | EstimationEffortRisk |