The Practical Guide to Defect Prevention

Conclusion

Consider this:

• A defect prevented will never need to be fixed, saving time, resources, and money for your organization.

• A defect prevented will improve the quality of your software and help increase customer satisfaction.

• A defect prevented will not impact customers and decrease their satisfaction with your software.

These simple statements represent why we wrote this book and the value we hope you receive from reading it.

Although the benefits can be significant, the effort often required to achieve high levels of defect prevention can be significant as well. Our hope is that the practical defect prevention techniques described in this book will help you minimize the effort, maximize the benefit, and more rapidly become a “prevention ...