View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Waste Analysis | ![]() Facilitation Dot Estimation | ![]() Agile Planning Poker |
|---|---|---|---|
Purposedifferent | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | 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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitysame | Low | Low | Low |
Timedifferent | 45-120 min | 5-20 min | 2-5 min je Item |
Participantsdifferent | 2-8 | 3-20 | 3-9 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | Effort Heatmap, Risk Signals, Discussion Targets | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | WasteLeanProcess improvement | EstimationEffortRisk | EstimationAgileRelative sizingTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






