Beyond Jira: Decode that Control Chart
summary
Claims that Jira Control Chart cycle plots are misleading for Scrum and that cycle time is useful only after translation to Scrum specifics. Demonstrates with a month of team data: histograms show a mode away from zero, histogram shape follows Troy McInness patterns, and a size vs time scatter reveals a predictable core plus long outliers. Numbers: low correlation for many items, a few multi-week outliers drive variance. Recommendation: split work, remove dependencies, treat blocked time as part of the measure.
AI-written summary · about
chapters (14)
- 0:00Data-driven project management
- 1:08Cycle time in project management
- 4:42Cycle time origins
- 5:48Jira control charts limits
- 7:34Cycle time data uses
- 9:22Cycle time distributions
- 10:48January sprint case study
- 12:18Practical cycle time applications
- 13:06Q&A
- 15:22Q&A: Outliers and tracking
- 17:12Q&A: Task splitting
- 19:05Q&A: Cycle time vs estimates
- 20:31Q&A: External dependencies
- 21:58Q&A: Blocked time
related talks
44mPredictably Agile
24mCycle Time is the only metric that counts
43mPredictable Delivery
20mHow to Communicate Metrics to Build Engagement
46mEstimates and complexity: a tale in 42 and a half minutes
01h 04mIs Agile Still the Answer? Lessons from Real World Agility
36mThe Development Metrics You Should Use (but Don’t)
01h 32mPNSQC 2014 - Hillel Glazer