View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Dot Estimation |  Facilitation Stakeholder Salience Model |  Agile Bucket System |  Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | 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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | When a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 5-20 min | 60-90 min | 30-90 min | 30 min Setup, dann laufend |
Participantsdifferent | 3-20 | 3-6 | 3-12 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Workshop | Workshop | Async |
Outputdifferent | Effort Heatmap, Risk Signals, Discussion Targets | Salience Diagram, Strategy per Class | Bucketed Backlog, Relative Estimates, Split Candidates | RAID Log, Status Report Source |
Tagsno overlap | EstimationEffortRisk | StakeholdersFacilitationAlignmentGovernance | EstimationBacklogRelative sizing | RiskTrackingStakeholdersGovernance |