Why Your Bug Rate Isn’t a Code Problem: Engineering for Unstable Work Intake
summary
Claims that defect rate follows intake stability, supported by anonymized JIRA data: Q1 hits 4 stories to 1 bug, Q2 degrades to 2:1 when intake is unstable, worst weeks dip to 1 story : 4 bugs, and Q3 recovers to 3.4:1. Concrete fixes: enforce Definition of Ready, decouple content from code via CMS, use feature flags and environment isolation, measure story-to-bug as an observability signal; team shifts to frequent deploys (about four times per week) and sees meaningful defect reduction.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:59Bug rate and unclear requirements
- 3:43Clarify step in framework
- 7:17Understand step and intent measurement
- 9:48Nerdy details and team data
- 13:43Leadership playbook and soft skills
- 16:19Hardening framework as OS
- 18:28Summary
- 20:37Q&A
related talks
51mZero-bug policy success
11mOverhead, not downtrodden
36mHow to defuse a bomb Wait, I mean a bug
17mZero Bug Policy
36mHow programmers & testers can be productive
44mEnhancing the Performance of Engineering Teams
23mManaging diverse engineers for high-impact deliveries
45mAccelerating Software Delivery: Why Your Team Is Slowing Down