The document discusses the cost of poor quality in software development projects. It notes that the visible costs are small compared to the larger, less quantifiable costs represented by the bottom of the "quality iceberg". Fixing defects early in the requirements stage can be 1000 times cheaper than fixing them after launch. Common problems include poor requirements, feature creep, and unrealistic schedules. Small changes can require significant testing and documentation efforts across teams. The quality team aims to ensure a flawless experience for customers by analyzing defects, automating testing, and continually improving processes through defect analysis and baselining applications.

1. Cost of Quality By Ankur Gupta

2. Agenda What is cost of “Poor” Quality? Why to find and fix defects early? Typical problems in software development? Why are small changes big deal? QC team’s objective, activities and action plan?

3. Cost of Poor Quality Project Failure Costs The Obvious and visible costs are a small portion. The bottom of the iceberg represents the major cost and Is not easily Quantified. Testing

4. Minimum Total Costs Minimum Total Costs

5. Cost of Quality The "cost of quality" isn't the price of creating a quality product or service. It's the cost of NOT creating a quality product or service.

6. Relative cost to fix an error The cost to fix a defect found on Live site may be as high as 1000 times the cost to fix it during the requirements stage

7. Common problems in the software development process Poor requirements – hard to get things done when you do not know what you want. Featuritis - requests to add new features after development goals are agreed on Unrealistic schedule Miscommunication

8. Small changes – Big Efforts Impact analysis and scoping. Testing UI Functional etc On different environments – QC, Staging, live Recording the change Documentation Analysis Development and systems/Network teams efforts.

9. Quality Team’s Objective Happy customers and flawless experience. Sanity is always maintained for the live site. Defect analysis and continual improvement. No site crashes or performance problems

10. Quality Team’s Activities Analyzing defects reported by other teams/users. Requirement analysis and test cases creation for new projects. Updating manual and automated test cases. Regression testing. - verifying defect fixes on live and local environments. Performance testing. Cross browser validations.

11. Action Plan Increased traceability from requirements to final delivery Defect recording and analysis to build quality product in first attempt. Baselining application and creating central knowledge repository. Testing automation for greater efficiency and reliability.

12. Conclusion QC team prevents crashing into poor quality ICEBERG We find defects early to keep costs down. We help improve efficiency by continual improvement and analysis.

13. Quality has no Finish line

14. Software Life Cycle

15. Is Perception Reality?

16. THANK YOU [email_address] 9910699578