Debugging Engineering Velocity
summary
Defines engineering velocity as precision speed quality impact and gives concrete fixes: create a cloud efficiency metric (cloud spend / business), focus a cohort so you get “10 delighted users” rather than dilute effort, cut WIP with colored-sprint goals, use Accelerate metrics (lead time, change frequency, failure rate, MTTR), run a four‑week reliability surge to stop pages, audit failures to raise deploy success 20% → 99%, and iterate to get a 35% tail latency reduction for a popular API.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:02I don't understand the impact of my work
- 1:55Motivational Theory
- 5:031. Analyze 2. Identify 3. Debug
- 7:10Planning: Alignment
- 8:55Planning: Prioritization
- 14:14Execution: Focus
- 16:00Execution: Speed
- 18:03Execution: Unblock (people)
- 20:54Execution: Unblock (systems)
- 23:09Execution: Quality
- 25:14Delivery
- 28:40Debugging Engineering Velocity
related talks
18mEngineering owns velocity
10mAchieving engineering velocity by optimising developer experience
41mEscape Velocity - Better Metrics for Software Teams
36mDoubling Engineering Productivity at eBay Through DevOps
31mImproving engineering effectiveness: A journey for the entire organization
48mVelocity Deep Dive
59mSet Your Teams Up for Improved and Enduring Velocity
15mOptimizing the engineering value stream