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 Shape Up | ![]() Facilitation Dot Estimation | ![]() Architecture Architecture Decision Record | ![]() Agile Ideal Days |
|---|---|---|---|---|
Purposedifferent | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 6 Wochen Cycle + 2 Wochen Cool-Down | 5-20 min | 15-45 min | 15-60 min |
Participantsdifferent | 2-4 pro Pitch | 3-20 | 1-3 | 2-9 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Effort Heatmap, Risk Signals, Discussion Targets | ADR File, Decision Log, Rationale | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | PlanningDeliveryAutonomy | EstimationEffortRisk | ArchitectureRationaleDocumentationGovernance | EstimationEffortAgile |



