Zero Defects – A philosophy

A software defect is an error, flaw, mistake, failure, or fault in a computer program that produces an incorrect or unexpected result. Most defects arise from mistakes and errors made by people in either a program's design or code. They arise from oversights or misunderstandings made by a software team during specification, design, coding, data entry and documentation. Software team here includes every

Software defects have significant costs associated with them – money, time, resources, and lost reputation for all parties involved in the project. Programs to eliminate defects can be expensive and time consuming.

In such case, Project managers generally have two options
1. Insist on eliminating all the defects at any cost
2. Accept that certain number of defects is acceptable, just bear the costs and learn to live with them?

Eliminitating all defects no matter what the costs – achieving Zero Defects.
"Zero defects." – is a phrase which was coined by Philip Crosby in his 1979 book titled, "Quality is Free." His position was that where there are zero defects, there are no costs associated with issues of poor quality; and hence, quality becomes free.


Explaining the Idea
Zero defects is a way of thinking and doing which reinforces the notion that defects are not acceptable, and that everyone should "do things right the first time" across all stakeholders. This would help in increasing profits by eliminating the costs of failure and increasing revenues through increased customer satisfaction.

"Zero defects" is referred to as a philosophy, a mentality or a movement. It's not a program, nor does it have distinct steps to follow or rules to abide by. This is perhaps why zero defects can be so effective, because it means it's adaptable to any situation, business, profession or industry.
Zero defects is not bout being perfect. It is philosophy that motivates everyone to do things right the first time. Zero defects is about changing the perspective of all stakeholders by

• Recognizing the high cost of quality issues
• Continuously thinking of where and how new defects might occur
• Work proactively to address such defects in the software and the processes, which allow defects to occur.

When buying a used car also, u take the car in for brake service, you expect that the mechanic will install the parts exactly as the manufacturer prescribes. No defect is an acceptable defect when it affects you personally.

So why then, is it so easy to accept that "defects happen" when you are the one producing the product or providing the service? This is the interesting dichotomy that presents itself. Zero defects is one of the best ways to resolve the discord between what we expect for ourselves and what we can accept for others.

Management must commit to zero defects. Zero defects requires a top down approach: The best-intentioned employees cannot provide zero defects if they are not given the tools to do so.