Issue Log Management

Distinguishing Issues, Risks, and Changes

On any project, especially in construction, you're constantly dealing with things that deviate from the plan. For the PMP exam, it's critical to be precise with your terminology. Are you dealing with a risk, an issue, or a change request? These are not interchangeable terms.

Let's look at a table that clearly separates these concepts based on their relationship to time: past, present, and future.

As the table shows:

• Risks are about the future. They are uncertain events that might happen. We plan for them proactively in a risk register.
• Issues are about the present. They are problems or questions that are happening now and are hindering the project. A risk, if it occurs, becomes an issue. However, many issues also arise unexpectedly without ever having been identified as risks.
• Changes are about the past. They are formal requests to revise something that was already approved, often as a result of an issue's resolution.

The Praizion video you'll watch next offers the official PMI definition, which is vital for the exam.

The key takeaway is that an issue is a current condition that needs to be addressed. While a risk you’ve been tracking might materialize and become an issue, many issues simply appear unexpectedly. For the exam, if a question describes a problem happening now, you should immediately think "issue."

The Issue Log: Your Tool for Tracking and Visibility

Once an issue is identified, where do you put it? You can't rely on memory, emails, or sticky notes. The formal project document for this is the issue log. Think of it as a central, shared ledger for all project problems. Its purpose is to ensure that every issue is documented, assigned an owner, and tracked through to its resolution.

Both the video and the article from Project Management Pathways detail the essential fields that make up an effective issue log.

By combining this with the video's explanation, we can compile a comprehensive list of what an issue log must contain:

• Issue Identifier: A unique number for tracking.
• Issue Description: A clear, concise statement of the problem.
• Date Raised & Reporter: When the issue was identified and by whom.
• Priority/Severity: How urgently this needs to be addressed. This helps in triaging multiple issues.
• Assigned Owner: The single individual responsible for ensuring the issue is resolved. This is a crucial element of accountability.
• Target Resolution Date: A deadline for resolving the issue.
• Status: The current state of the issue (e.g., Open, Under Investigation, Pending Action, Resolved, Closed). This makes the log a dynamic tracking tool.
• Final Solution: A summary of the action taken to resolve the issue, which becomes part of the project's knowledge base.

For the PMP exam, remember this important fact: The issue log is first created as an output of the Direct and Manage Project Work process. This is a common exam topic.

From Logging to Solving: A Systematic Approach

Logging an issue is only half the battle. The ultimate goal is resolution. The PMP exam expects you to demonstrate a logical, structured approach to problem-solving, not just ad-hoc firefighting.

The Praizion video outlines an excellent six-step method derived directly from PMI principles. It even provides a handy acronym: DIGC-IV.

Let's break down the DIGC-IV framework with a practical construction example. Imagine the issue is: "The concrete pour for the second-floor slab, scheduled for tomorrow, cannot proceed because the rebar delivered is the wrong grade."

1. Define the Problem: Clearly state the problem and its immediate impact. "Wrong grade of rebar delivered. Second-floor concrete pour delayed, impacting the critical path."
2. Identify the Root Cause: Investigate why it happened. Was it an error in the purchase order? Did the supplier make a mistake? Was the spec misread? A root cause analysis (using a technique like the 5 Whys, which we'll cover later) might reveal the purchase order clerk was working off an outdated drawing.
3. Generate Possible Solutions: Brainstorm options with the team.
   • Option A: Return rebar and wait for the correct grade (major schedule delay).
   • Option B: Have the structural engineer evaluate if the delivered rebar can be used, perhaps with additional reinforcement (potential cost/scope change).
   • Option C: Source the correct rebar from an alternate, local supplier at a premium price (cost impact).
4. Choose the Best Solution: Analyze the options based on their impact on project constraints (scope, schedule, cost, quality). Let's say the team decides on Option C as it has the smallest schedule impact, which is the primary concern.
5. Implement the Solution: Execute the chosen plan. Issue a new purchase order to the local supplier, arrange for expedited delivery, and update the short-term work plan.
6. Verify Solution Effectiveness: Confirm the problem is truly solved. The correct rebar arrives on-site, passes inspection, is installed, and the concrete pour proceeds, albeit one day late. The issue log is updated to "Closed."

If the chosen solution (e.g., using a more expensive supplier) impacts the project's budget baseline, it would require a formal change request to be submitted to the change control process. This link between the issue log and the change control process is a crucial concept for the PMP exam.

Conclusion

In this lesson, we have established the formal PMI process for managing project problems. This structured approach moves problem-solving from a reactive scramble to a controlled management discipline.

Here are the key takeaways for your PMP exam preparation:

• Issues are current problems that are happening now, distinct from future-oriented risks and past-focused changes.
• The Issue Log is the central project document used to track all issues from identification to resolution.
• A complete issue log entry includes a description, priority, assigned owner, target date, and status.
• The issue log is an output of the Direct and Manage Project Work process.
• Use a structured problem-solving method like DIGC-IV (Define, Identify, Generate, Choose, Implement, Verify) to address issues systematically.
• Resolving an issue may lead to a change request, which must follow the formal integrated change control process.

This lesson concludes the first module on PMI Foundations. You now have a solid understanding of the PMP exam itself, the PMI mindset, the role of the project manager, and the fundamental tool for handling day-to-day problems—the issue log.

In our next lesson, we will begin Module 2 by exploring the environment in which projects exist. We will learn to differentiate between Enterprise Environmental Factors (EEFs) and Organizational Process Assets (OPAs), two key concepts that define the context and constraints for any project you manage.