PMP · Question #949
A project lead is managing a construction project in an isolated location. There have been delays due to difficult working conditions, which include team sickness and absences. How should the…
The correct answer is B. Identify the causes of the issues in order to find a suitable solution. To get a delayed project back on track due to team sickness and absences, the project lead should first identify the root causes of these issues to find suitable solutions.
Question
Options
- AAsk for additional budget because the project end will be delayed.
- BIdentify the causes of the issues in order to find a suitable solution.
- CReview the project scope in order to simplify it and shorten project duration.
- DAsk human resources (HR) to find individuals to replace team members.
How the community answered
(15 responses)- B80% (12)
- C13% (2)
- D7% (1)
Why each option
To get a delayed project back on track due to team sickness and absences, the project lead should first identify the root causes of these issues to find suitable solutions.
Asking for additional budget addresses the *symptom* of delay (and its cost implication) rather than the root cause of the operational issues causing the delay.
Before attempting any solution, it is crucial for the project lead to thoroughly investigate and understand the root causes of the team sickness and absences. This allows for the development of targeted, effective solutions that address the underlying problems, such as poor working conditions or lack of safety, rather than just treating symptoms, which is essential for sustainable recovery and getting the project back on track.
Reviewing the project scope is a potential strategy for schedule recovery, but it is not the immediate or primary step to address delays specifically stemming from team health and presence issues.
Requesting HR to find replacements is a reactive measure that doesn't address the underlying reasons for the current team's sickness and absences, which could recur with new team members or indicate deeper systemic problems.
Concept tested: Issue management and root cause analysis
Source: https://learn.microsoft.com/en-us/project/manage-issues
Topics
Community Discussion
4B is the correct answer. Before you can fix a problem you have to root-cause it, and PMP wants you in that problem-solving mindset before you touch budget or scope. A and C are premature reactions because you do not yet know what is driving the sickness and absences, so throwing money or cutting scope is guessing. D is a knee-jerk escalation to HR that ignores your job as project lead to assess the isolated working conditions first and find a suitable, informed solution.
B is correct here because root cause analysis is step one before you touch budget, scope, or headcount, and PMI wants you solving the actual problem rather than throwing resources at symptoms. That said, has anyone seen a recent exam variant where the stem explicitly states the causes are already known, and if so does that flip the answer to a corrective action option instead?
Going with D, in an isolated location you need bodies on site fast.
Respectfully, B is the correct answer here. Remote locations with limited infrastructure are exactly the scenario where automated scheduling tools deliver the most value, since they optimize resource allocation and coordination without relying on manual processes that break down when you cannot get people on site quickly.