Download this free Root Cause Analysis template and use it for your new project. Scroll down to the bottom of the page for the download link.
<This section shall identify the overall purpose of this document and its intended audience.>
<This section shall identify the scope of this document.>
<This section shall describe any acronyms used in this document. >
<This section shall identify the documents related to the products that already exist.>
<This section shall identify all internal and external standards that will be adhered to in the development of the system. This will also identify those external standards that have been specified by the customer. In case there are corresponding internal standards, this section shall outline the reasons for not using the internal standards.>
<This section provides a description of the event that is being analyzed. It provides a clear and concise description of the problem that triggered this Root Cause Analysis. It should state the date, time, detailed description of the event/problem, who detected the problem, who it affected, and how it affected them. It is important that the descriptions are as detailed as possible since this problem is the source of the entire RCA.>
<In this section you are to provide a detailed chronology of the events leading up to, and following, the problem. This is an important piece of the RCA as the chronology of events may lead to clues in determining how or why the problem occurred. Be sure to include names, times and detailed descriptions of all activities.>
Click Here to download 3000+ Project Management Documents: Complete Library of Project Management Templates, Processes, Plans, Checklists, Forms, Tools, Presentation Slides and Infographics. Suitable For All Industries.
Table 1 : Chronology of Events/ Timeline Table
<This section should describe how the investigative team is assembled, who it consists of, and how it gathers the data to be used in the analysis. As with any process, it is important in the RCA that clear roles and methodologies be established in order to allow for the process to move in a controlled and deliberate manner. This is also an important part of the RCA because a majority of time spent in RCA is gathering data about the event/problem. >
<This section should describe the findings of the investigation and explain the root cause(s) based on these findings. It is possible that a RCA results in findings that are not directly related to the root cause of the problem. These should also be captured as product/process improvement steps in an effort to improve the product/project. It is important to note that this section does not describe the corrective actions to be taken as a result of identifying root cause. Corrective action will be discussed separately in the next paragraph. All findings must be formally communicated with the project team in order to ensure any project changes can be made in accordance with the project’s change management process.>
<As the purpose of the RCA is to determine the root cause of a problem, it should result in some corrective actions that may be taken to ensure the same problem is not repeated. Often, these corrective actions will result in changes to a project’s scope, schedule, or cost. It is imperative that all of the findings and corrective actions are detailed and formally communicated with the project team so changes can go through the change management process and be implemented in the project plan upon approval.>
Click here to download Root Cause Analysis Template.