Why do you need to analyze root causes
Agile development has Kaizen, continuous process improvement, in its heart. The speed of agile delivery hits borders defined by company organization, company’s processes and environment.
The primary role of ScrumMasters and agile managers is to optimize development flow from end to end. The impediments (blockers) are in many agile companies just gathered or solved immediately without deeper analysis. This many times lead to solving minor issues, but not the most important one.
Root cause analyze
Root cause analyze is a technique to find out the real reason of a problem.
For example, your problem is that your customers are not satisfied. Why? Because of lack of quality, late delivery and maybe that results are different than expected. But why these reasons exist? Ask another why question and you will find that there are some common reasons for multiple problems. They will probably even create some loops (see Causal Loops Diagram). And if these loops are solved, then suddenly top problem will start to fade away.
Here is another example of root cause analysis where we identified as the reason of low customers’ satisfaction as missing vision and no time to define it on customer’s side and not SW vendor.
How to do RCA?
- Put your problem as the first node in your mind map in RCA Desk.
- There are multiple techniques how to understand the root cause of your problem. The simplest one (and probably the most efficient) is very simple. 5 WHY – just ask Why? question up to five times for every node in your analysis.
- Draw additional connections if any node is related to other nodes. One node can be related/depending on multiple others.
- Try to identify loops in your RCA that should be broken as the first step.
- Identify tasks for those loops that should be done to solve root causes and add tasks to the WORK view.