Scribd
Upload
15 views13 pages

Root Cause Analysis Process

Root Cause Analysis (RCA) is a problem-solving method aimed at identifying the fundamental causes of faults to prevent recurrence. The process involves a series of steps including defect reporting, analysis, and corrective measures, utilizing techniques like the '5 Whys' to explore cause-and-effect relationships. Implementing RCA can improve software quality, reduce costs, and enhance process efficiency across various areas such as production and user acceptance testing.

Uploaded by

Rai Shahzad Kharal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
15 views13 pages

Root Cause Analysis Process

Root Cause Analysis (RCA) is a problem-solving method aimed at identifying the fundamental causes of faults to prevent recurrence. The process involves a series of steps including defect reporting, analysis, and corrective measures, utilizing techniques like the '5 Whys' to explore cause-and-effect relationships. Implementing RCA can improve software quality, reduce costs, and enhance process efficiency across various areas such as production and user acceptance testing.

Uploaded by

Rai Shahzad Kharal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 13

Root Cause

Analysis Process
Overview
What is RCA?

A root cause is the fundamental


Root Cause analysis is a method of
breakdown or failure of the process
problem-solving that tries to identify
which, when resolved, prevents a
the root causes of faults or problems.
recurrence of the problem.

For significant and high-risk issues,


root cause analysis should be Through this approach, we can mature
performed with the recommended from defect detection to
approach for effective identification of defect prevention.
root causes and the right action plan.
Benefits:
• Helps in determining and identifying
main causes of the problem
• Eliminate future recurrence of the
problem with action plans
• Establish repeatable and appropriate
Root Cause step-by-step processes
Analysis(RCA) • Problems are prevented in other areas
• Improves software quality by minimizing
number of defects
• Saves cost and effort
• Improves process efficiency
• Identifies process improvements
RCA Steps

1. Support Team reports critical defect post release and creates ticket in JIRA

2. Scrum Master sets up a quick call including Dev Lead, QA Lead, Scrum Master and
Support Team to triage the bug

3. QA reviews/updates the following defect details in JIRA


a. Problem Statement
b. Customer Impact
c. Severity
d. Priority
e. High level root cause

4. Dev Team will do thorough Analysis and fix within 24 hours

5. QA Team will repro the defect, categorize and do retro on missing the test case/scenario
RCA steps continued …

6. Dev Team will fix the bug, QA Team will validate, update any
existing test cases/add bug regression test cases as necessary

7. Once defect is fixed, QA Team will call for ‘Root Cause Analysis’
meeting with the following members.
- QA Lead
- Dev Lead
- Product Owner
- Scrum Master
- Support Team

8. QA Lead will gather Corrective and Preventive Measures to


develop the RCA document using the “5 Whys” guidelines
5 Whys
Definition:
The 5 Whys is an iterative question-asking technique used to explore the cause-and-
effect relationships underlying a particular problem. The primary goal of the technique is
to determine the root cause of a defect or a problem. (The "5" in the name derives from
an empirical observation on the number of iterations typically required to resolve the
problem)

Define the Action of the


Why is it happening 1 ? Why 2 Why 3 Why 4 Why 5
problem: problem
RCA Example 1
RCA Example 1
RCA Example 2
RCA Document Example
RCA Documentation and Communication

- QA Lead attaches the completed RCA document with appropriate JIRA


defect(s) and links Bug regression Test cases if any.

- QA Lead stores the RCA documents at a Centralized location


https://confluence.asicentral.com/display/PROJ/Root+Cause+Analysis

- QA Lead Circulates the RCA Document to Project Stake Holders and IT


Executives (including CTO)
Other Areas where we can implement RCA
process

• Production – Post Release

• UAT - Regression Cycle

• As necessary in other areas


Questions / Comments

Thank You!!!

You might also like