This site uses cookies , both own and third parties , to collect statistical information about your browsing and show related advertising to your preferences , generated from your navigation patterns . If you go on surfing, we will consider you accepting its use.

Examples how to move towards Zero Defects

How many defects should the users of our software find? How many issues do you accept the users to experience? If you agree that it should be “Zero!”, then we can discuss how to achieve that. If you think it’s impossible, better attend and learn, to avoid being put out of business by those who are delivering Zero Defects.

Some people think that we can produce better quality by better testing. Wrong! The most economical way to produce quality is by preventing any problems to creep in in the first place, making sure the users don’t experience any hassle. We’ll discuss a few cases where we used techniques that helped people move towards Zero Defects, like: design, review, the DesignLog, short-circuiting, and using “No Questions, No Issues” as a final test requirement.

Zero Defects is often is dismissed as an impossible dream. My experience tells otherwise. It doesn’t mean “turning a switch and then we don’t produce bugs anymore”. What it does mean you will find out in the presentation.