Skip to content
PMPCAPM

Root Cause Analysis

Root cause analysis is a technique used to identify the fundamental underlying reason for a variance, defect, or risk, with the goal of eliminating the root cause rather than just treating symptoms.

Share:

Explanation

Root cause analysis (RCA) is used across multiple project management knowledge areas, but it is particularly important in quality management. The technique systematically investigates why a problem occurred by looking beyond the immediate symptoms to find the underlying cause. Common RCA methods include the "5 Whys" technique (asking "why" repeatedly until the root cause is found), cause-and-effect diagrams, fault tree analysis, and failure mode and effect analysis.\n\nThe goal of RCA is to address the fundamental cause of a problem so that it does not recur. Treating symptoms without addressing root causes leads to recurring problems and wasted resources. For example, if a software application has frequent crashes, fixing each crash individually treats symptoms, while identifying and fixing the underlying memory management flaw addresses the root cause.\n\nRCA is used in both Manage Quality and Control Quality processes. In Manage Quality, it helps improve processes that are not performing well. In Control Quality, it helps understand why defects are occurring so that corrective and preventive actions can be taken.

Key Points

  • Identifies fundamental causes rather than treating symptoms
  • Common methods include 5 Whys, cause-and-effect diagrams, and fault tree analysis
  • Used in both Manage Quality and Control Quality
  • Goal is to prevent recurrence by eliminating the underlying cause

Exam Tip

When the exam presents a recurring problem, the correct first step is usually to perform root cause analysis before taking corrective action. PMI wants you to understand the cause before fixing the symptom.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Earned Value Management (EVM)

Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.

Power/Influence Grid

The power/influence grid is a stakeholder classification model that groups stakeholders based on their level of authority (power) and their active involvement or ability to affect the project (influence).

Part of

Quality Management

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.