Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Different Root Cause Analysis Techniques and Tools

DZone's Guide to

Different Root Cause Analysis Techniques and Tools

· Agile Zone ·
Free Resource

The Agile Zone is brought to you in partnership with Techtown Training. Learn how DevOps and SAFe® can be used either separately or in unison as a way to make your organization more efficient, more effective, and more successful in our SAFe® vs DevOps eBook.


It’s common to see people point fingers and play the blame game after a project fails. These blame games not only hurt the team members but also impact their morale as well. Is there a way to avoid these hurtful situations while focusing on improving process and identifying the failure’s root cause? 

The answer to that question can be found with root cause analysis (RCA), which helps to divert attention from people to process improvement.

Typically, agile teams are recommended to do an RCA session in response to issues raised during retrospectives. Shamefully, many agile teams skip RCA and continue to struggle in a whirlwind of issues.

RCA is not rocket science—especially when we have such a simple tool as the five whys. Eric Ries has elaborated on RCA with some practical examples from his lean startup journey. Here’s an example of a simple Excel spreadsheet that shows how to conduct RCA using the five whys; you can download a ready-to-use spreadsheet here.

Read the complete article on Techwell.

 

Adopting a DevOps practice starts with understanding where you are in the implementation journey. Download the DevOps Transformation Roadmap, brought to you in partnership with Techtown Training

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}