Experience in delivery project with Zero Defects. - An intelligent Plan - Monitoring with a Quest for Quality - Building a Learning Team

1. Experiences in Delivering Project with Zero Defects SrikanthRao July 2010

2. Usual Reactions on Zero Defects in Software Projects July 10 “Are you kidding me?. It is a miracle. How can we expect zero defects in software development? It is harder to define, harder to test, harder to predict results. Bugs is a perfectly normal thing, we can’t bring them to zero. But we should minimize them using all possible ways. ”The Last Bug is a mirage” Like any other PM, I started with a “Zero Defects Mentality” which is not about having zero bugs as a target (as you're never sure of achieving it), but about doing all that's necessary to prevent bugs. Then the “Zero Defect software Delivery” happened!. I guess I got lucky(?). The purpose of the ppt is to share some best practices that were used to pursue the “Zero Defect Mentality”. Luck is probably a dividend of sweat! The author was also instrumental in architecting the Quality Management System for a Global software company and had co-authored the V-Process model

3. My Experience in Managing a Zero Defect Project July 10

6. Built contingency for course correction; e.g. Internal Schedule was tighter than schedule committed to customer“The more intelligently you plan, the luckier you get.” July 10

10. Every week was a deadline; The “True Status” should be determined by the PM based on his/her assessment of the quality of the deliverables rather than relying on the status reported by the team member. July 10

12. Challenged the Team to deliver a zero-defect Unit tested Code (where the PM cannot find errors).

14. Support to meet deadlines/Debugging“A work output of a Developer working under two different Project Managers (PMs) is different. The PM who demands quality would not only get a better output but would also be valued by the Team Members for adding value to them and enabling their professional development .” July 10

16. Development Environment different from Production environment

17. Two hardware Dongles (for a team of 10); Team worked in shifts

18. Frequent Power Outage

20. Zero Defect during UAT