The Development Metrics You Should Use (but Don’t)
summary
Collect start and finish dates for each work item and plot time-in-process as a scatter or distribution to see that 50% of items took about three weeks while 90% confidence sits near two months, revealing big variability. Separate failure demand (some had a mandatory 45‑day floor) and measure throughput (months showed counts like 9 9 11 6 4 6 4 10 13). Expect ~5% process cycle efficiency value touch time, use simple WIP tokens (Legos) and limit WIP to improve predictability.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:45Breakfast Is the Most Important Meal of the Day
- 2:38Quality Responsiveness Productivity and Predictability
- 8:00Measure Time and Process
- 26:33Aging of the Working Process
- 30:01Productivity
- 33:35Processed Cycle Efficiency
- 34:17Wait Time Non-Value-Added Activities
- 39:53Leading Indicator
- 46:43Temper Expectation
related talks
36mThe Development Metrics You Should Use (but Don’t)
41mThe Development Metrics You Should Use (but Don’t)
44mAgile metrics for predicting the future
30mHow to Visualize Impacts to Your Workflow & Metrics
45mOne Metric to Rule them All: Cycle Time
43mPredictable Delivery
31mTime Theft: Using Flow Metrics to Expose Crimes from Conflicting Priorities and Unplanned Work
16mPractically predictable – Forecasting delivery when nothing is certai