The 30 Days of Agile Testing Day 27 task is:
Research zero bug tolerance, and discuss on The Club on the value of this approach
What do you think of this approach?
Zero bug tolerance seems like a good idea. But… What is the value of fixing all the bugs instead of doing something else? I agree with 30 Days of Agile Testing – Zero Bug Tolerance – offbeattesting.
1 Like
According to this article: Zero Bug Tolerance: Improve software quality with one simple practice | by Marek Kirejczyk | EL Passion Blog | Medium , I think the benefit that comes with this approach is that it reduces the pile-up of bugs in the backlog, also lower priority bugs may be based upon some non-functional testing, however when they are piled up, the app will end up with some real performance issue and that’s when a P1 is raised
I liked the zero bug tolerance approach. To eliminate any possible misunderstanding between zero bug tolarence and absence–of–errors fallacy. This approach is about fixing found bugs, absence-of-errors fallacy is mentionaning that a system or a product definetly has bugs which is undiscovered.
In theory it looks great, there may be adaptations needed because developer mindset is not always about fixing bugs but create new features. Improving this approach with encouraging elements for the team memberst to fix all the bugs would be great!
Its a good way to prevent the situation of low-prio bugs cluttering up your backlog.
Either fix them now or accept their existence.
Also, immediate fixing is easier probably, as people are still familiar with what was worked on. This can change if a bug is picked up weeks later.
1 Like