Root Cause Analysis

A problem-solving method that identifies the fundamental reason behind a variance, defect, or risk. A single root cause can lead to multiple variances, defects, or risks.

Key Points

  • Traces symptoms back to their source using techniques like 5 Whys, fishbone (Ishikawa) diagrams, and fault tree analysis.
  • Aims to prevent recurrence by fixing causes rather than treating symptoms.
  • One cause may drive several issues across scope, schedule, cost, quality, or risk.
  • Outputs inform corrective and preventive actions, change requests, risk responses, and lessons learned updates.

Example

On a construction project, multiple walls fail inspection due to incorrect dimensions, causing rework and schedule slippage. The team performs root cause analysis and finds that outdated drawings were distributed to several crews. They correct the document control process, retrain staff, and issue a change request to prevent further defects.

PMP Example Question

A project is experiencing recurring test failures and rising cost variance. What should the project manager use to discover the fundamental reason and prevent recurrence?

  1. Trend analysis
  2. Root cause analysis
  3. Reserve analysis
  4. Fast tracking

Correct Answer: B — Root cause analysis

Explanation: Root cause analysis is used to identify the underlying reason for defects or variances so the team can implement targeted preventive and corrective actions.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Seven sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Launch your career!

HK School of Management provides world-class training in Project Management with AI and Agile Methodologies. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More