PMP · Question #31
A project is being delayed due to a large amount of rework caused by a quality problem that is impacting the critical path. What should the project manager do?
The correct answer is D. Report the delay with rectifying actions to the change control board (CCB) for review.. The project manager should report the critical path delay and proposed rectifying actions to the change control board (CCB) for formal review because changes impacting the critical path and requiring significant rework often necessitate a formal change request.
Question
A project is being delayed due to a large amount of rework caused by a quality problem that is impacting the critical path. What should the project manager do?
Options
- AReport the delay with rectifying actions to the project management office (PMO).
- BRebaseline the project schedule to absorb the delay.
- CNotify the project steering committee about the cause of the delay.
- DReport the delay with rectifying actions to the change control board (CCB) for review.
How the community answered
(35 responses)- A9% (3)
- B3% (1)
- C6% (2)
- D83% (29)
Why each option
The project manager should report the critical path delay and proposed rectifying actions to the change control board (CCB) for formal review because changes impacting the critical path and requiring significant rework often necessitate a formal change request.
While reporting to the PMO is important, the PMO primarily provides governance and support, whereas a formal change to a critical path requires a decision from the Change Control Board.
Rebaselining the project schedule without formal approval from the CCB is premature and bypasses the established change control process.
Notifying the project steering committee about the cause of the delay is part of stakeholder communication, but it doesn't address the formal process for managing significant changes to the project baselines.
A quality problem causing significant rework and impacting the critical path constitutes a significant deviation from the project baseline. Such issues typically require a formal change request to be submitted to the Change Control Board (CCB) for their review, approval, or rejection, as it affects scope, schedule, or cost baselines. The CCB is responsible for evaluating and managing all proposed changes to the project.
Concept tested: Project Change Control Process
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/control-changes-to-project-baselines
Topics
Community Discussion
5D. Any rework hitting the critical path means a schedule change, and schedule changes go through the CCB, not the PMO or steering committee. Rebaselining without approved formal change control is exactly what the PMBOK warns against.
Got D on my exam last month. The keyword combo is rework plus critical path, which means a schedule change is required, and any schedule change has to go through the CCB, not the PMO or steering committee.
Agreed on D, but to be precise it is not every schedule change that goes to the CCB, only ones that affect the baseline, and a critical path shift definitely qualifies.
Leaned toward B at first since rebaselining sounded like the quick fix. But any schedule change due to rework has to go through the CCB, so D is the correct answer.
D is right but the real driver is that any approved change to the schedule baseline requires a formal CCB decision, not just rework in isolation.