The document outlines the author's experience in delivering a zero-defect software project and emphasizes the importance of a 'zero defects mentality' in software development. It details strategies for intelligent planning, quality monitoring, and team-building aimed at minimizing defects while encouraging professional growth. Key practices include rigorous code reviews, peer testing, and motivating the team through challenges and rewards.

1. Experiences in Delivering Project with Zero DefectsSrikanthRaoJuly 2010

2. Usual Reactions on Zero Defects in Software ProjectsJuly 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 ProjectJuly 10

4. Planning Intelligently – Key StrategiesInch-stone – A finer way to control MilestonesInch-stone – “Sub-task deliverables within the existing Mile-stones”

5. Developed a finer degree of scheduling oversight that enabled early detection of potential delaysEarly Risk Mitigation DeliverablesConverted risks (Technical, Schedule, Quality risks) into Early Risk Mitigation Deliverables e.g. Planned early delivery of critical componentsPlanning for Learning & ContingencyScheduled Time/Activities for focused/improved learning

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

7. Monitoring with a Quest for Quality – Key Strategies“Mentoring Reviews” – Focus on improving the AuthorRigorous “Mentoring Review” with a focus on improving Author; Demanded Perfection;

8. 100% Code Reviews by PM; Did not delegate reviewsPeer Testing and “Pair Design”Peer testing: Team members tested each others code. We termed it as Cross Testing

9. “Pair Design”: A term coined from “Pair Programming” where two people did the design working on the same workstation. Weekly Deadline Orientation Completion of an inch-stone defined clearly - item must pass the “Review”;

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

11. Building a Learning Team – Key StrategiesDaily Team Meetings – Working as a TeamFormal Daily team Meetings – Status Check; Sharing of Learning; Resolving issuesChallenging The Team – Motivation to LearnDemanding Perfection

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

13. Fun Prizes (Chocolates) for finding more number of defects during Peer TestingMentoring & Coaching – Support to Learn“Mentoring Reviews” – Genuine focus to improve the author

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

15. The ProjectJuly 10Effort : About 2.5 person years; Peak Team Size; 11 peopleThe Constraints Simulated development environment.

16. Development Environment different from Production environment

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

18. Frequent Power Outage

19. 9 out of 10 members were fresh from college The EnablersStable RequirementsResults All Deliveries on time

20. Zero Defect during UAT

21. Two enhancement requests during UATThank YouSrikanthRao106, Sobha Opal, 39th Cross, 18th main, 4T Block Jayanagar, Bangalore98450 48400Quotable Quotes“In NASA, we never punish error. We only punish the concealment of error.” - Al Siepert“Obstacles are things a person sees when he takes his eyes off his goal.” E. Joseph Cossman“Limitations live only in our minds. But if we use our imaginations, our possibilities become limitless.” Jamie Paolinetti“In the same degree you are helpful, you will be happy”Karl ReilandJuly 10