# Root Cause Analysis (RCA)

**#rootcauseanalysis** **#rca** **#5whys** **#fishbone** [**Prasun Das**](https://www.linkedin.com/in/prasun-das/)

Root Cause Analysis (**RCA)** is a structured and effective process to find the root cause of issues in a Software Project team. If performed systematically, it can improve the performance and quality of the deliverables and the processes, not only at the team level but also across the organization.

### **Advantages of Root Cause Analysis**

*   Prevent the reoccurrence of the same problem in the future.
    
*   Eventually, reduce the number of defects reported over time.
    
*   Reduces developmental costs and saves time.
    
*   Improve the software development process and hence aid quick delivery to market.
    
*   Improves customer satisfaction.
    
*   Boost productivity.
    
*   Find hidden problems in the system.
    
*   Aids in continuous improvement.
    

### **Steps To Do Root Cause Analysis**

*   Form RCA Team.
    
*   Define The Problem - Use the **SMART** rule to define your problem.
    
*   Identify Root Cause - Use the **Fishbone diagram** or **5 Why Analysis** method or both to arrive at the root cause(s).
    
*   Implement Root Cause Corrective Action (**RCCA**) - Correction action involves giving a fix to the solution by identifying the real root cause(s).
    
*   Implement Root Cause Preventive Action (**RCPA**) - The team needs to come up with a plan for how such a similar issue can be prevented in the future.
    

### **Root Cause Analysis Techniques**

*   **5 Whys Technique** - 5 Why technique is used standalone or as part of a fishbone diagram to drill down to the root cause of the problem. The number of steps is not limited to 5. It can be less or more than 5 until the diagnosis of the problem has arrived. 5 Whys are relatively a simpler technique and a faster way to arrive at the root causes. It facilitates quick diagnosis to rule out the symptoms and arrive at the root cause.
    
*   **Fishbone diagram** (Ishikawa Diagram) -  Fishbone diagram is a visual root cause analysis tool to identify the possible causes of the identified problems hence it’s also called the Cause and Effect diagram. It allows you to get down to the real root cause of the issue rather than solving its symptom. The Fishbone diagram resembles the skeletons of a fish with the **problem forming the head of the fish** and **causing forming the spine and bones of the fish**.
    

* * *

Here we have RCA with 2 very common scenarios which may be arises time-on-time within any project using both the 5 Whys Technique and the Fishbone diagram (see below);

### **Example 1: Production release rollback**

5 Whys Example

![Fig 1: 5 Whys Example with Production Release Rollback](https://media.licdn.com/dms/image/v2/D5612AQH81kGmT1CHlg/article-inline_image-shrink_1500_2232/article-inline_image-shrink_1500_2232/0/1688928432744?e=1776902400&v=beta&t=b49UPdXd2KTWsf32q--eVgfLSZToQMYHBHB-TAhKxSU align="center")

Fig 1: 5 Whys Example with Production Release Rollback

Fishbone Diagram

![Fig 2: Fishbone Diagram with Production Release Rollback](https://media.licdn.com/dms/image/v2/D5612AQHpCkUoa_gSYg/article-inline_image-shrink_1500_2232/article-inline_image-shrink_1500_2232/0/1688928701493?e=1776902400&v=beta&t=O9cxvP0y1lf3ur_Q2LdGcvFAndQggvkkjPNSg0HXmxA align="center")

Fig 2: Fishbone Diagram with Production Release Rollback

* * *

### **Example 2: Sprint ticket spillover**

5 Whys Example

![Fig 3: 5 Whys Example with Sprint Ticket Spillover](https://media.licdn.com/dms/image/v2/D5612AQFsHtqjGzh7QQ/article-inline_image-shrink_1500_2232/article-inline_image-shrink_1500_2232/0/1688929122067?e=1776902400&v=beta&t=5vjM4C-rmk55AQPXGy8aJM4AwlAWqEIANqxGjSUAtPc align="center")

Fig 3: 5 Whys Example with Sprint Ticket Spillover

Fishbone Diagram

![Fig 4: Fishbone Diagram with Sprint Ticket Spillover](https://media.licdn.com/dms/image/v2/D5612AQEqBBZ9SfDFow/article-inline_image-shrink_1500_2232/article-inline_image-shrink_1500_2232/0/1688929318292?e=1776902400&v=beta&t=ePGOlp268ZBeVhxBpr6nom6jjJmcmKEwA1wfbJnnRnI align="center")

Fig 4: Fishbone Diagram with Sprint Ticket Spillover

* * *

### **Pareto Chart**

![Fig 5: Pareto Chart Example](https://media.licdn.com/dms/image/v2/D5612AQEkd2jc6zPt8Q/article-inline_image-shrink_1500_2232/article-inline_image-shrink_1500_2232/0/1688929756301?e=1776902400&v=beta&t=9BkRrDK8UmFoL_RLzD2y3LMkUAz16hu9PnjCbj42qBw align="center")

Fig 5: Pareto Chart Example

* * *

"Remember, Learning is a journey, not a destination." - [**Prasun Das**](https://www.linkedin.com/in/prasun-das/)

* * *

Published Version: 1.1 Copyright [**Prasun Das**](https://www.linkedin.com/in/prasun-das/)