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.

Agile Project Management & Scrum — With AI

Ship value sooner, cut busywork, and lead with confidence. Whether you’re new to Agile or scaling multiple teams, this course gives you a practical system to plan smarter, execute faster, and keep stakeholders aligned.

This isn’t theory—it’s a hands-on playbook for modern delivery. You’ll master Scrum roles, events, and artifacts; turn vision into a living roadmap; and use AI to refine backlogs, write clear user stories and acceptance criteria, forecast with velocity, and automate status updates and reports.

You’ll learn estimation, capacity and release planning, quality and risk management (including risk burndown), and Agile-friendly EVM—plus how to scale with Scrum of Scrums, LeSS, SAFe, and more. Downloadable templates and ready-to-use GPT prompts help you apply everything immediately.

Learn proven patterns from real projects and adopt workflows that reduce meetings, improve visibility, and boost throughput. Ready to level up your delivery and lead in the AI era? Enroll now and start building smarter sprints.



Stop Managing Admin. Start Leading the Future!

HK School of Management helps you master AI-Prompt Engineering to automate chaos and drive strategic value. Move beyond status reports and risk logs by turning AI into your most capable assistant. Learn the core elements of prompt engineering to save hours every week and focus on high-value leadership. For the price of lunch, you get practical frameworks to future-proof your career and solve the blank page problem immediately. Backed by a 30-day money-back guarantee-zero risk, real impact.

Enroll Now
``` ### Marketing Notes for this Revision: * **The Hook:** I used the "Stop/Start" phrasing from your landing page description because it creates a clear transformation for the user. * **The Value:** It highlights the specific pain point mentioned in your text (drowning in administrative work) and offers the "AI Assistant" model as the solution. * **The Pricing/Risk:** I kept the "price of lunch" and "guarantee" messaging as it is a powerful way to reduce friction for a Udemy course. Would you like me to create a second version that focuses more specifically on the "fear of obsolescence" mentioned in your landing page info?