Root cause Analysis of Defects
6 likes5,406 views
Root Cause Analysis (RCA) is a process to understand the underlying causes of problems in order to prevent future issues. It involves asking "Why?" repeatedly to determine the root cause, typically requiring around 5 iterations. RCA principles include making it continuous, focusing on prevention over blame, and always searching for the root cause rather than stopping at surface explanations. Common leakage reasons for defects include requirements ambiguity, insufficient testing, and outdated test coverage. RCA stats can be used to measure quality and determine where to focus process improvements.
Root cause Analysis of Defects
- 1. Root Cause Analysis of Defects Speaker David Gevorgyan
- 2. Main Topics 4RCA principles 5Leakage reason 6Corner case 7Preventive actions 8How to use RCA stats? 9Q & A 1What is RCA? 2How to do RCA? 3When to do RCA? 2
- 3. What is RCA? It’s a process designed to understand the causes of problems and improve product by preventing issues of the ineffective areas of the software development processes
- 4. 4How to do RCA? 5 Whys technique 5 Whys is technique which goal is to determine the root cause of a defect or problem by repeating the question "Why?" Each question forms the basis of the next question. The "5" in the name derives from an empirical observation on the number of iterations typically required to resolve the problem. Why? Why? Why? Why? Why?
- 5. 5How to do RCA? Imagine that we have fixed an issue, that users with apostrophe symbol in “First name” field were unable to save changes in their profile page.
- 6. 6How to do RCA? Why we've received an issue? Why Save button is not working on users page? Why does specific symbol affect on save button? Why the issue not have been detected by manual QA? Why the issue not have been detected by automation QA?
- 7. 7When to Start Doing RCA? 3 It’s fun It’s easy 2 1 It’s cheap Short answer is: As soon as you can!
- 8. 8RCA Principles 1 RCA should be continuous. Lack of time is false economy ⏳ 2 We should always remember that RCA goal is to prevent new issues, not finger pointing🏆 3 Always search the root of a problem, never stop after first “why” 🚀 4 It’s better to prevent bugs than fix 🔗 5 RCA is not about story telling ✇
- 9. 9RCA of Defects Leakage reason Root cause to determine method defect escaped the testing phase Preventive action Action taken to reduce or eliminate the probability of defects from happening in the future.
- 10. 10Leakage Reason 3 Insufficient manual testing Automation defect 2 1Requirement Ambiguity 6Missing coverage (Area/Scenario/Corner case) Outdated coverage 5 4Environment issues (Hardware, software or configurations)
- 11. 11Corner Case Is a case which the cost-benefit ratio is very low.
- 12. 12Preventive Actions 3 Governance Automation coverage 2 1 Coverage 6None Training 5 4Process improvement
- 13. 13How to do RCA? 5 Whys technique Why we've received an issue? Why Save button is not working on users page? Why does specific symbol affect on save button? Why the issue not have been detected by manual QA? Why the issue not have been detected by automation QA?
- 14. 14How to use RCA Stats? Collect RCA stats to measure the quality Based on the results of RCA, you can determine which of the phase has problem areas. For example, if you determine most of the RCA of the defects are due to requirement miss, then you can improve the requirement gathering / understanding phase by introducing more reviews or walk-through sessions. Similarly if you find that mostly defects are due to testing miss, you need to improve the testing process. You can introduce metrics like requirement traceability metrics, test coverage metrics or can keep a check on the review process or any other step which you feel would improve the efficiency of the testing. It is the responsibility of the entire team to sit and analyze the defects, and contribute to the product and process improvement. 1 Risk identification Solve Real Problems2 3 Support continuous improvement
- 15. Issue fixing Here developer gives a feedback about what was the problem and how he fixed the issue Issue verification and deploying Issue verification and deployment stage RCA RCA is done by Manual QA engineer. Manual QA Engineer can: • submit an issue for automation test, • add coverage, • escalate the problem to management and try to change the current process.