Tools for Root Cause Analysis (eBook)
€4.99 (Excl. VAT)
How to effectively analyze problems to identify the main causes that have led to them, and to initiate actions to prevent similar problems from occurring in the future.
Practical processes, templates, checklists, and examples.
Author: Ben Linders
Dec 29, 2016
Frequently Bought Together
Over the years, I’ve been asked many times for a hands-on solution to do Root Cause Analysis (RCA). I have described a process and a checklist to help organizations that want to start with it, and I’m providing a report with an example. Together they form this mini booklet.
The purpose of Root Cause Analysis is to analyze problems to identify the main causes that have led to them, and to initiate actions to prevent similar problems from occurring in the future. RCA helps you to take a system view, and understand what has happened. An RCA sessions can be done on any problem; often it is done on defects that were found by customers or during test, on major project disturbances, or findings from earlier (CMMI, risk, agile, or other) assessments.
Root Cause Analysis has been used for many years to determine a fault’s first or “root” causes in order to identify process improvement opportunities that give a quick ROI. If you have any question on Root Cause Analysis, or experiences doing Root Cause Analysis, feel free to reach out to me!
Note: This booklet replaces and extends the separate downloads that were available for RCA support (process, template, example, checklist).