No Questions, No Issues. Period!
How many defects would you like to find? How many issues would you accept the users to experience? If you agree with me that the answer should be “Zero!”, then we can discuss how to achieve that. If you think that it’s impossible, you better come and listen, otherwise your team may gradually be put out of business by those who did learn to achieve Zero Defects.
Of course it’s the development team that should prevent defects and make sure the users don’t experience any problem. Some testers fear that if there are no defects, they may not be needed anymore. Don’t worry. We should better discuss what the testers can do to help the developers to achieve this goal. Testing becomes even more challenging and interesting if no issues are found.
Once we deliver our software or our system to users, we’re not there to answer any questions or solve problems when they occur. It should simply work, without any problems. When introducing the concept of Zero Defects, one of the techniques I use is to suggest as a challenge that at final test there should be “no questions, no issues”. If the testers would have even just one question to ask, or if they would find even just one issue, the test is to be aborted as failed. My experience is that in no time the quality of the deliveries improves dramatically.
I’ll show you two cases where I challenged the developers and testers with the “no question, no issue” requirement. The first case was a Scrum team that succeeded immediately in the next sprint. In the other case a developer/tester team had been doing ‘system test’ after ‘system test’ for months, every time uncovering new problems. It took a few iterations for the team (developers and testers together) to find out my requirement was dead serious, but then then quality increased dramatically and they could finally deliver successfully to the customer.
No questions. No issues.Niels_Malotaux_ForPublication1