O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Cost Of Quality

4.158 visualizações

Publicada em

Presentation to explain the cost of quality and why to spend on testing/QA

Publicada em: Software

Cost Of Quality

  1. 1. Cost of Quality By Ankur Gupta
  2. 2. Agenda <ul><li>What is cost of “Poor” Quality? </li></ul><ul><li>Why to find and fix defects early? </li></ul><ul><li>Typical problems in software development? </li></ul><ul><li>Why are small changes big deal? </li></ul><ul><li>QC team’s objective, activities and action plan? </li></ul>
  3. 3. Cost of Poor Quality Project <ul><li>Failure Costs </li></ul><ul><li>The Obvious and visible costs are a small portion. </li></ul><ul><li>The bottom of the iceberg represents the major cost and </li></ul><ul><li>Is not easily Quantified. </li></ul>Testing
  4. 4. Minimum Total Costs Minimum Total Costs
  5. 5. Cost of Quality <ul><li>The &quot;cost of quality&quot; isn't the price of creating a quality product or service. It's the cost of NOT creating a quality product or service. </li></ul>
  6. 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. 7. Common problems in the software development process <ul><li>Poor requirements – hard to get things done when you do not know what you want. </li></ul><ul><li>Featuritis - requests to add new features after development goals are agreed on </li></ul><ul><li>Unrealistic schedule </li></ul><ul><li>Miscommunication </li></ul>
  8. 8. Small changes – Big Efforts <ul><li>Impact analysis and scoping. </li></ul><ul><li>Testing </li></ul><ul><ul><li>UI </li></ul></ul><ul><ul><li>Functional etc </li></ul></ul><ul><ul><li>On different environments – QC, Staging, live </li></ul></ul><ul><li>Recording the change </li></ul><ul><ul><li>Documentation </li></ul></ul><ul><ul><li>Analysis </li></ul></ul><ul><li>Development and systems/Network teams efforts. </li></ul>
  9. 9. Quality Team’s Objective <ul><li>Happy customers and flawless experience. </li></ul><ul><li>Sanity is always maintained for the live site. </li></ul><ul><li>Defect analysis and continual improvement. </li></ul><ul><li>No site crashes or performance problems </li></ul>
  10. 10. Quality Team’s Activities <ul><li>Analyzing defects reported by other teams/users. </li></ul><ul><li>Requirement analysis and test cases creation for new projects. </li></ul><ul><li>Updating manual and automated test cases. </li></ul><ul><li>Regression testing. - verifying defect fixes on live and local environments. </li></ul><ul><li>Performance testing. </li></ul><ul><li>Cross browser validations. </li></ul>
  11. 11. Action Plan <ul><li>Increased traceability from requirements to final delivery </li></ul><ul><li>Defect recording and analysis to build quality product in first attempt. </li></ul><ul><li>Baselining application and creating central knowledge repository. </li></ul><ul><li>Testing automation for greater efficiency and reliability. </li></ul>
  12. 12. Conclusion <ul><li>QC team prevents crashing into poor quality ICEBERG </li></ul><ul><li>We find defects early to keep costs down. </li></ul><ul><li>We help improve efficiency by continual improvement and analysis. </li></ul>
  13. 13. Quality has no Finish line
  14. 14. Software Life Cycle
  15. 15. Is Perception Reality?
  16. 16. THANK YOU [email_address] 9910699578