ExamFinch.com My Study

Study guide

5.7 Managing Project Issues

Practice this exam

Project Management Professional PMP

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Fundamentals

1.1 About the PMP Exam 1.2 What is a Project? 1.3 Project, Program & Portfolio Management 1.4 The Project Manager Role 1.5 PMBOK 7 Principles Overview 1.6 Performance Domains Overview 1.7 What Changed in the July 2026 PMP Exam

2 Chapter 2: People Domain Part 1

2.1 Managing Conflict 2.2 Leading a Team 2.3 Supporting Team Performance 2.4 Empowering Team Members 2.5 Training & Development 2.6 Building a Team 2.7 Removing Impediments

3 Chapter 3: People Domain Part 2

3.1 Negotiating Project Agreements 3.2 Collaborating with Stakeholders 3.3 Building Shared Understanding 3.4 Engaging Virtual Teams 3.5 Defining Team Ground Rules 3.6 Mentoring Stakeholders 3.7 Emotional Intelligence

4 Chapter 4: Process Domain - Planning

4.1 Determining Project Methodology 4.2 Integrating Project Planning 4.3 Planning & Managing Scope 4.4 Planning & Managing Schedule 4.5 Planning & Managing Budget 4.6 Planning & Managing Quality 4.7 Planning & Managing Resources 4.8 Planning & Managing Procurement

5 Chapter 5: Process Domain - Execution & Control

5.1 Executing with Urgency for Value 5.2 Managing Communications 5.3 Assessing & Managing Risks 5.4 Engaging Stakeholders 5.5 Managing Project Changes 5.6 Establishing Project Governance 5.7 Managing Project Issues 5.8 Managing Project Artifacts 5.9 Knowledge Transfer & Closure

6 Chapter 6: Business Environment Domain

6.1 Planning & Managing Compliance 6.2 Evaluating & Delivering Benefits 6.3 External Environment Changes 6.4 Supporting Organizational Change

7 Chapter 7: Agile & Hybrid Approaches

7.1 Agile Mindset & Values 7.2 Scrum Framework 7.3 Kanban & Lean 7.4 Extreme Programming (XP) 7.5 Hybrid Project Management 7.6 Agile Planning & Estimation 7.7 Agile Metrics & Tools

8 Chapter 8: Predictive (Waterfall) Approaches

8.1 Predictive Lifecycle 8.2 Scope Management 8.3 Schedule Management 8.4 Cost Management 8.5 Quality Management 8.6 Risk Management Process 8.7 Procurement & Contracts 8.8 Change Control

5.7 Managing Project Issues

Key Takeaways Explain This Topic AI

An issue is a current problem or matter that requires resolution, unlike a risk which is an uncertain future event

The Issue Log is a project document that tracks all identified issues, their status, owners, and resolution activities

Root Cause Analysis (RCA) identifies the fundamental source of problems to prevent recurrence rather than just treating symptoms

The Five Whys technique involves asking 'why' repeatedly to drill down from symptoms to root causes

Collaborative approaches to issue resolution leverage diverse team perspectives and build shared ownership of solutions

Last updated: January 2026

Issues are current problems that need attention, unlike risks which are uncertain future events. Effective issue management ensures problems are identified early, analyzed properly, and resolved before they derail the project.

Issues vs. Risks

Understanding the distinction between issues and risks is fundamental:

  • Characteristic Issue Risk
  • Timing Current, happening now Future, may or may not occur
  • Certainty Known, certain Uncertain
  • Response Resolution required Response planned
  • Document Issue Log Risk Register
  • Urgency Needs immediate attention Can be planned for

A risk that occurs becomes an issue. Effective risk management reduces issues; effective issue management resolves them.

The Issue Log

The Issue Log is a project document used to track and monitor issues throughout the project lifecycle.

Issue Log Components

  • Component Description Example
  • Issue ID Unique identifier ISS-001
  • Description Clear statement of the issue "Server cannot handle load"
  • Category Type of issue Technical, Resource, External
  • Date Identified When discovered 2026-01-09
  • Raised By Who identified the issue Team member name
  • Priority Urgency level Critical, High, Medium, Low
  • Issue Owner Responsible for resolution Named individual
  • Target Resolution Date When it should be resolved 2026-01-15
  • Status Current state Open, In Progress, Resolved, Closed
  • Resolution How it was resolved Actions taken
  • Lessons Learned Knowledge gained Insights for future
  • Issue Priority Levels
  • Priority Description Response Time
  • Critical Project stoppage, major impact Immediate
  • High Significant impact on delivery Within 24-48 hours
  • Medium Moderate impact, workarounds exist Within 1 week
  • Low Minor impact, can be scheduled Within project timeline
  • Issue Management Process
  • Standard Issue Management Flow
  • Identify : Recognize and document the issue
  • Categorize : Classify by type and priority
  • Assign : Designate an issue owner
  • Analyze : Investigate root cause
  • Develop Options : Identify possible solutions
  • Decide : Select resolution approach
  • Implement : Execute resolution actions
  • Verify : Confirm issue is resolved
  • Close : Document and capture lessons learned
  • Issue Escalation

When issues cannot be resolved at the project level:

  • Follow governance escalation paths
  • Provide complete information to decision-makers
  • Recommend solutions when possible
  • Track escalated issues through resolution
  • Root Cause Analysis (RCA)

Root Cause Analysis is a systematic process for identifying the fundamental source of problems. RCA focuses on addressing underlying causes rather than treating symptoms.

Why RCA Matters

  • Without RCA With RCA
  • Symptoms are treated Causes are eliminated
  • Problems recur Problems are prevented
  • Reactive firefighting Proactive improvement
  • Wasted resources on repeated fixes Sustainable solutions
  • RCA Core Principles
  • Focus on remedying causes rather than symptoms
  • Realize there may be multiple root causes
  • Focus on how and why , not who
  • Be systematic and methodical
  • Find cause-and-effect evidence
  • Take a comprehensive approach
  • Root Cause Analysis Techniques
  • The Five Whys

The Five Whys technique involves asking "why?" repeatedly (typically five times) to drill down from symptoms to root causes.

Example:

  • Level Question Answer
  • Problem The deployment failed
  • Why 1? Why did it fail? The database connection timed out
  • Why 2? Why did it time out? The query took too long
  • Why 3? Why was the query slow? The table wasn't indexed
  • Why 4? Why wasn't it indexed? It wasn't in the deployment checklist
  • Why 5? Why wasn't it on the checklist? We don't have a review process for schema changes
  • Root Cause : Lack of review process for database schema changes
  • Corrective Action : Implement schema change review process
  • Fishbone Diagram (Ishikawa Diagram)

The Fishbone Diagram (also called cause-and-effect diagram) visualizes potential causes organized by category.

Standard Categories (6 M's for Manufacturing):

  • Manpower : People, skills, training
  • Methods : Processes, procedures
  • Machines : Equipment, technology
  • Materials : Inputs, data, resources
  • Measurements : Metrics, criteria
  • Mother Nature/Environment : External factors

Adapted Categories for Projects:

  • People : Skills, availability, communication
  • Process : Methods, workflows, procedures
  • Technology : Tools, systems, infrastructure
  • Resources : Budget, materials, equipment
  • External : Vendors, regulations, environment
  • Other RCA Techniques
  • Technique Description Best For
  • Change Analysis Compare before/after a change Issues following changes
  • Barrier Analysis Identify where controls failed Process failures
  • Pareto Analysis 80/20 rule for prioritization Multiple issues
  • Fault Tree Analysis Top-down logic diagram Complex system failures
  • Collaborative Issue Resolution

Effective issue resolution leverages team collaboration:

  • Benefits of Collaborative Approach
  • Diverse perspectives : Different viewpoints uncover causes
  • Shared understanding : Team aligns on problem and solution
  • Buy-in : Involvement creates ownership
  • Better solutions : Collective wisdom outperforms individual
  • Knowledge sharing : Team learns together
  • Collaborative Techniques
  • Technique Description When to Use
  • Brainstorming Generate ideas without judgment Initial exploration
  • Affinity Grouping Organize ideas into themes Large number of inputs
  • Dot Voting Prioritize options Selecting among alternatives
  • Round Robin Each person contributes in turn Ensure all voices heard
  • Nominal Group Technique Structured idea generation and voting Balanced participation
  • Creating a Blame-Free Environment

For effective issue resolution:

  • Focus on what happened , not who
  • Treat issues as learning opportunities
  • Encourage reporting without fear
  • Celebrate identification of issues
  • Recognize problem-solvers
  • Issue Management Best Practices
  • Practice Description
  • Act quickly Address issues before they escalate
  • Assign ownership Every issue needs an owner
  • Track systematically Use the Issue Log consistently
  • Communicate regularly Keep stakeholders informed
  • Escalate appropriately Know when to involve others
  • Learn continuously Capture lessons from every resolution
  • Prevent recurrence Address root causes, not just symptoms
  • Key Takeaways
  • Issues are current problems requiring resolution; risks are future uncertainties
  • The Issue Log tracks all issues through identification to resolution
  • Root Cause Analysis prevents recurrence by addressing fundamental causes
  • The Five Whys and Fishbone Diagram are key RCA techniques
  • Collaborative approaches yield better solutions and team buy-in