The Development Metrics You Should Use (but Don’t)
summary
Uses start and end dates to compute time in process per item and plots a scatter of delivery date vs duration to show trends rather than single averages. Reports concrete probabilities: 90% = 53 days, 50% ≈ 3 weeks for one team, and exposes a bimodal pattern where failure demand ≥45 days skews estimates. Adds monthly throughput bars, applies Little’s Law to compare arrival vs departure rates, automates an “expedite” email that reduced urgents and subsequent quality issues, and recommends counts not story points.
AI-written summary · about
chapters (7)
- 0:00Intro
- 4:26Time in process
- 9:09Why probability?
- 17:12Throughput
- 23:18Trade offs
- 26:47Positive vs. negative net flow
- 35:57Outro
related talks
41mThe Development Metrics You Should Use (but Don’t)
49mThe Development Metrics You Should Use (but Don’t)
44mAgile metrics for predicting the future
43mPredictable Delivery
51mGet Predictability Regardless of Estimates
23mThe Shape of Uncertainty
16mPractically predictable – Forecasting delivery when nothing is certai
14mI don't think these metrics mean what you think they mean!