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 |  Agile T-Shirt Sizing |  Operations Theory of Constraints |  Operations After-Action Review |
|---|---|---|---|---|
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. | When effort only needs to be classified roughly, it makes comparability more important than false precision. It helps sort work quickly into manageable sizes. | For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | laufend, 1-5 min je Item | 15-45 min | 2-4 h Analyse, laufend | 20-45 min |
Participantsdifferent | 3-9 | 2-12 | 3-12 | 3-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Size Buckets, Rough Backlog Map, Split Candidates | Constraint Map, Improvement Plan, Flow Metrics | Lessons learned, Action items, Event summary |
Tagsno overlap | EstimationAgileMeasurement | EstimationAgileRoadmap | OperationsConstraintsFlowImprovement | LearningOperationsImprovement |