Problem Analysis: Root Cause and Optimization Techniques

PMBOK v8 Definition

Problem Analysis is a systematic approach used to identify the underlying causes of issues, variances, defects, or risks in a project. It employs analytical methods such as root cause analysis, five whys analysis, SWOT analysis, and branch and bound to move beyond symptoms and discover fundamental reasons for problems. When all root causes are removed, the problem does not recur.

Why It Matters for the Exam

Problem Analysis techniques appear frequently in PMI exam questions related to risk management, quality management, and issue resolution. You will encounter these in situational questions where you must select the appropriate analysis technique to identify the true cause of a project problem, distinguish between symptoms and root causes, or determine the optimal solution path.

Key Points to Remember (for the exam)

• Root Cause Analysis: An analytical method to determine the basic underlying reason causing a variance, defect, or risk. One root cause may underlie multiple variances or defects.

• Five Whys Analysis: An iterative brainstorming technique that repeatedly asks "why" to move beyond symptoms to the root cause of the problem.

• SWOT Analysis: Analyzes strengths, weaknesses, opportunities, and threats of an organization, project, or option. Used to increase breadth of identified risks by including internally generated risks.

• Branch and Bound: An optimization problem-solving method that breaks problems into smaller subproblems and uses bounding functions to eliminate subproblems that do not contain the optimal solution.

• Starbursting: A brainstorming technique with six points (who, what, when, where, why, how) to generate questions about an idea or issue from different angles.

• Reverse Brainstorming: A technique where teams create ideas about how to make a problem worse instead of solving it, which may help identify root causes.

• Common Confusion: Root cause analysis identifies WHY a problem occurred, while branch and bound finds the OPTIMAL solution path. Five whys is specifically iterative questioning, not a single analysis step.

Typical PMI Exam Example

During project execution, your team encounters recurring defects in deliverables. Initial investigation shows multiple symptoms. Which technique should you use to move beyond these symptoms and identify the fundamental reason for the defects? → Five whys analysis, because it iteratively asks "why" to reach the root cause.

PMI Exam Traps

• Trap: Confusing root cause analysis with five whys analysis

  • Reality: Root cause analysis is the broader method; five whys is a specific technique within root cause analysis

• Trap: Thinking branch and bound is for identifying causes

  • Reality: Branch and bound is for finding optimal solutions, not for root cause identification

• Trap: Assuming SWOT analysis only examines external factors

  • Reality: SWOT includes internal strengths and weaknesses, plus external opportunities and threats

• Trap: Confusing starbursting with mind mapping

  • Reality: Starbursting generates questions from six angles (who, what, when, where, why, how); mind mapping diagrams thought processes

Important PMI Connections

Quick Review Questions

1. Which technique repeatedly asks "why" to move beyond symptoms to the root cause of a problem?

2. What is the primary purpose of branch and bound in problem analysis?

3. During SWOT analysis, what is examined to determine if organizational strengths may offset threats?

4. What are the six points of starbursting, and what do they represent?

5. When all root causes for a problem are removed, what is the expected outcome?

PMBOK v8 Reference

Section 11.2 - Identify Risks (Risk Management Knowledge Area) — Problem Analysis techniques including SWOT analysis, root cause analysis, and five whys analysis are used as tools and techniques for risk identification and problem resolution.