Zero Defect Software
Experiences in Delivering Project with Zero Defects
Srikanth Rao
Usual Reactions on Zero Defects in Software Projects
“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
July 10
2
My Experience in Managing a Zero Defect Project
July 10
3
Planning Intelligently – Key Strategies
Inch-stone – A finer way to control Milestones
• Inch-stone – “Sub-task deliverables within the existing Mile-stones”
• Developed a finer degree of scheduling oversight that enabled early detection of potential delays
Inch-stones
Early Risk
Mitigation
Deliverables
Early Risk Mitigation Deliverables
• Converted risks (Technical, Schedule, Quality risks) into Early Risk Mitigation
Deliverables e.g. Planned early delivery of critical components
Planning for
Learning &
Contingency
Planning for Learning & Contingency
• Scheduled Time/Activities for focused/improved learning
• Built contingency for course correction; e.g. Internal Schedule was tighter than schedule committed to customer
An Intelligent Plan
“The more intelligently you plan, the luckier you get.”
4
July 10
Monitoring with a Quest for Quality – Key
Srikanth Rao
Usual Reactions on Zero Defects in Software Projects
“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
July 10
2
My Experience in Managing a Zero Defect Project
July 10
3
Planning Intelligently – Key Strategies
Inch-stone – A finer way to control Milestones
• Inch-stone – “Sub-task deliverables within the existing Mile-stones”
• Developed a finer degree of scheduling oversight that enabled early detection of potential delays
Inch-stones
Early Risk
Mitigation
Deliverables
Early Risk Mitigation Deliverables
• Converted risks (Technical, Schedule, Quality risks) into Early Risk Mitigation
Deliverables e.g. Planned early delivery of critical components
Planning for
Learning &
Contingency
Planning for Learning & Contingency
• Scheduled Time/Activities for focused/improved learning
• Built contingency for course correction; e.g. Internal Schedule was tighter than schedule committed to customer
An Intelligent Plan
“The more intelligently you plan, the luckier you get.”
4
July 10
Monitoring with a Quest for Quality – Key