Zero bug policy

The premise of zero bug policy is to redefine what is classified as a bug. Peter Hilton explains that the aim of the zero bug policy is to fix bugs before adding any new code. Switching gears frequently to fix bugs and test the new code can lead to unpredictable development timelines, which a zero bug policy can help to address. 

Within my company, bugs are called “live issues” and are immediately documented as user stories. This means that they get prioritised alongside all other user stories, so they carry the same value (in theory). So bugs are categorised as follows: 

Bugs found during regression testing can point to a gap in testing: for example, tests were not updated when some requirements were changed. These, too, are categorised as user stories and can be prioritised accordingly.

A Zero Bug Policy might sound like a dream. Imagine opening the bug tracker and seeing nothing waiting. But the idea is not about chasing perfection or pretending that bugs no longer exist. It is more about changing how teams treat bugs. Instead of letting them pile up in a forgotten corner, this approach encourages every bug to be looked at, talked about and acted upon.

The real goal is to stop bugs from going stale. When a bug is reported, it should either be fixed, deferred with reason, or closed with clarity. Nothing should sit idle just because no one knows what to do with it. That is where this policy helps. It keeps things clean and clear. It tells the team that bugs are not just noise but signals that need attention.

This does not mean the software will be flawless. Bugs can and will show up. But under a Zero Bug Policy, they are not allowed to hang around without a plan. Every bug has a story. Either it is fixed, it is acknowledged as not worth fixing right now, or it is tagged with a reason and safely closed.

For testers, this brings a sense of closure. It shows that their findings are respected. Their work is not vanishing into a backlog that no one checks. For developers, it brings focus. They deal with the issues that matter right now rather than chasing ghosts from three releases ago.

This approach also invites a shift in mindset. It encourages quicker decisions, stronger triage habits and open conversations about priorities. It is not always easy. It requires effort, time and a team culture that believes in ownership and clarity. But when done well, it keeps the system healthy and the team aligned.

Zero Bug does not mean zero problems. It means zero silence around problems.