View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile Story Points | ![]() Operations A3 Problem Solving | ![]() Facilitation Dot Estimation | ![]() Operations Gemba Walk |
|---|---|---|---|---|
Purposedifferent | When teams want to rate complexity rather than hours, it creates a shared, relative scale. It sorts work by value, risk, and delivery ability. The result is captured as Point Estimates, Reference Stories, and Velocity Data. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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 there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | laufend, 1-5 min je Item | 45-90 min | 5-20 min | 30-120 min |
Participantsdifferent | 3-9 | 2-5 | 3-20 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | A3 Report, Action Plan, Root Cause Analysis | Effort Heatmap, Risk Signals, Discussion Targets | Observation Notes, Improvement Ideas |
Tagsno overlap | EstimationAgileMeasurement | LeanProblem solvingCoachingOperations | EstimationEffortRisk | LeanObservationProcessOperations |



