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 Views and Beyond | ![]() Facilitation Dot Estimation | ![]() Agile Ideal Days |
|---|---|---|---|---|
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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30 min Setup, dann laufend | 1-3 Tage | 5-20 min | 15-60 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-4 | 3-20 | 2-9 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Architecture Views, Cross-view Notes, Rationale | Effort Heatmap, Risk Signals, Discussion Targets | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | RiskTrackingStakeholdersGovernance | DocumentationStakeholdersArchitecture | EstimationEffortRisk | EstimationEffortAgile |



