Zero Bug Policy

on YouTube ↗17m

" summary

A Zero Bug Policy that treats every customer-facing failure as a bug and classifies reports as critical/bug/improvement so the product owner can prioritize. Small teams (3–9 developers) triage the backlog, interrupt ongoing work to fix important bugs quickly, and push fixes from a single deployable master branch. Reported results: faster visible fixes, higher product quality, fewer new bugs over time, and gradual adoption across three teams.

AI-written summary · about

" chapters (11)

1. 0:00Merci
2. 1:12Equipes
3. 1:31Gestion des bugs
4. 2:46Politique zéro bug
5. 3:55Classification
6. 4:09Problème critique
7. 5:52Priorisation
8. 6:31Comment commencer
9. 7:25Niveau de qualité
10. 9:10Pas facile
11. 11:54Chez nous

" related talks

• 51mZero-bug policy successPeter Hilton · Agile on the Beach 2025
• 22mWhy Your Bug Rate Isn’t a Code Problem: Engineering for Unstable Work IntakeEric Bible · Commit Your Code 2026
• 35mAvoiding the Petard: Triage at Scale in Firefox QuantumEmma Humphries · foss-north 2018
• 46mHow to Tame Bugs in Production: Successful Bug Managing Strategy in Five StepsElena Bazina · TestCon Europe 2021
• 11mBridging the gap between engineering and customer successAnnie Cook · LeadDev Austin 2019
• 34mZero defects, zero progressEwald Roodenrijs · Build Stuff 2016
• 11mOverhead, not downtroddenPenny Wyatt · The Lead Developer 2016
• 11mWorking with sharp tools - A case study of Continuous deploymentHaavard Gulbrandsen · Mobile Era 2017