Zero Bug Policy

A Zero Bug Policy moves a team’s output towards quality.

All bugs take priority over all new feature development or improvements.

The workflow is simple. Begin by going through your current issues and classifying bugs.

Move any bugs to the top of the backlog and start working on them.

The development team must not begin working on other items in the backlog until all bugs are cleared.

Software development schedules have no meaning with open bugs.

Fixing bugs first creates predictability.

The policy helps to reduce some of the uncertainty introduced by bugs from work ahead.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Rafael A. George Duval

Learning about software engineering through the lens of everything, one snippet of text at a time. Chief Editor: