PMP · Question #514
A project manager who is managing a critical project in a multinational company is conducting a progress meeting with all team members. During the meeting, one of the team members states that they are
The correct answer is B. Schedule a meeting with the concerned team member to review and update the issue log. When a team member reports a critical problem preventing task completion, the project manager should schedule a meeting to review and update the issue log. This ensures the problem is formally documented and managed for resolution.
Question
A project manager who is managing a critical project in a multinational company is conducting a progress meeting with all team members. During the meeting, one of the team members states that they are facing a critical problem that will prevent them from completing their assigned task. What should the project manager do?
Options
- AAsk the team member to follow the approved communications management plan to communicate
- BSchedule a meeting with the concerned team member to review and update the issue log
- CReview the risk register with the team member to find the proper response action for this issue
- DAsk the team member to raise a change request to assess the issue in detail
How the community answered
(35 responses)- A14% (5)
- B74% (26)
- C9% (3)
- D3% (1)
Why each option
When a team member reports a critical problem preventing task completion, the project manager should schedule a meeting to review and update the issue log. This ensures the problem is formally documented and managed for resolution.
While communication is key, simply asking them to follow the communication plan doesn't actively address or resolve the critical problem; the problem itself needs to be managed first.
A critical problem that has already occurred and is preventing task completion is an issue, not an uncertain risk. The immediate action is to formally log this issue and begin the process of addressing it, which typically involves a dedicated discussion to understand its full impact and develop a resolution plan. Updating the issue log is a standard project management practice for tracking and resolving current problems.
The problem has already occurred and is preventing task completion, making it an issue, not an uncertain risk; therefore, the risk register is not the primary tool for managing current problems.
A change request is typically initiated for changes to scope, schedule, or budget, or to implement a corrective action after an issue has been analyzed, not as the first step for reporting an operational problem.
Concept tested: Issue management and tracking
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok
Topics
Community Discussion
3B is correct. An issue is a problem that has already occurred, so it belongs in the issue log, not the risk register. Option C is a trap I see a lot because people confuse risks with issues, but risks are future events. Scheduling a follow-up to log and analyze the issue is the right move here. I made a card for this one with the cue "problem already occurred" on the front and "update the issue log" on the back, and the interval is holding steady at three weeks.
Leaned toward C first, but B is right because every problem needs the issue log.
Picked B on my exam last month. C is the trap because people see "critical problem" and jump to risk register, but the issue has already materialized so it goes in the issue log, not the risk register.