PK0-004 · Question #189
A change must be made to a project to comply with municipal code. The project manager updates the relevant shared project documents. The key stakeholders subsequently update the documents with new…
The correct answer is C. Version control processes were not applied. When shared documents are updated by multiple parties without version control, different stakeholders may be working from different document versions simultaneously, causing deliverables to be built or inspected against inconsistent specifications.
Question
A change must be made to a project to comply with municipal code. The project manager updates the relevant shared project documents. The key stakeholders subsequently update the documents with new information. When the project deliverables are reinspected, they fail the inspection. Which of the following is the MOST likely reason for the failed inspection?
Options
- AThere were insufficient resources assigned to the task.
- BThe prior document version was not reviewed.
- CVersion control processes were not applied.
- DThe CCB was not contacted.
How the community answered
(16 responses)- A13% (2)
- C81% (13)
- D6% (1)
Why each option
When shared documents are updated by multiple parties without version control, different stakeholders may be working from different document versions simultaneously, causing deliverables to be built or inspected against inconsistent specifications.
Insufficient resource assignment would affect the capacity or quality of work performed, but would not explain a document-driven discrepancy between what was built and what the current specification required.
Reviewing a prior document version is a symptom that can result from missing version control, but it describes a consequence rather than the root cause of the failed inspection.
Version control processes ensure that all project participants are referencing the single, authoritative, current version of project documents at all times. Without these controls, the project manager's updates and the stakeholders' subsequent updates could have created divergent document versions, meaning the deliverables were produced or evaluated against specifications that no longer aligned - directly causing the inspection failure.
The CCB manages the formal approval of change requests, but the failure here occurred after the change was already in progress - the breakdown was in document version management, not in change authorization.
Concept tested: Version control in project document management
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok
Topics
Community Discussion
No community discussion yet for this question.