Zero-bug policy success
summary
Small fully remote Norwegian startup builds a mobile‑first circular web shop and runs a yearlong experiment starting 1 May 2024 to chase zero open bugs, reaching zero bug day at the end of August. Six developers (five doing feature work), simple tools — a bugs Slack channel, Notion tracker, no Jira — and a weekly rotating first‑responder turn raw reports into tickets. Team fixes ~161 bugs in the main period (three prove critical), deletes ~9% of reports, and keeps weekly open bugs at 0–2, which eliminates prioritization fights and speeds debugging.
AI-written summary · about
chapters (10)
- 0:00Zero-bug policy intro
- 3:41Team and software context
- 7:35Starting the experiment
- 17:04Fixing 250 bugs in a year
- 26:11Zero Bug Day success
- 33:25Daily work with zero bugs
- 43:21Stakeholder concerns
- 46:33Lessons learned
- 51:50Why it works
- 52:13Q&A
related talks
51mZero-bug policy success
42m82 Bugs I Collected in a Year You Won’t Believe Made It to Production
10mBeyond “try harder”: Effective strategies to tackle bugs
36mHow to defuse a bomb Wait, I mean a bug
38mLearning from your bugs
01h 44mFirefox Bug Rodeo!
35m82 Bugs I Collected in a Year You Won’t Believe Made It to Production
35mAvoiding the Petard: Triage at Scale in Firefox Quantum