Overhead, not downtrodden
summary
Reframes overhead roles as levers not excuses: a QA team becomes a quality assistance team that trains developers, builds customer empathy and enforces accountability, cutting stories needing rework from 100% to 4%, eliminating a three‑month rework phase and enabling multiple weekly deploys while improving product quality. For bugfix, measurables from customer feedback (cancellations: 10% UX, 8% performance, 0.4% bugs) and a historic correlation of bug debt to headcount produce a target of 2.5 developers to keep debt stable, so resources get returned to higher‑impact work.
AI-written summary · about
chapters (5)
related talks
26mHelp! We have a QA problem
40mHelp! We Have a QA Problem!
58mDeveloper Joy – How Great Teams Get S%*t Done
25mDeveloper Joy – How great teams get s%*t done
18mAgile leadership and technical mastery, a harmonious alliance
45mAccelerating Software Delivery: Why Your Team Is Slowing Down
48mDeveloper Joy – How Great Teams Get s%*t Done
22mWhy Your Bug Rate Isn’t a Code Problem: Engineering for Unstable Work Intake