Explanation
According to the PMBOK Guide, document quality control is the process of ensuring that the project documents meet the quality standards and requirements of the project and the stakeholders. Document quality control involves the following activities:
Defining the quality criteria and specifications for the project documents, such as format, style, language, accuracy, completeness, consistency, etc.
Reviewing and inspecting the project documents to verify that they comply with the quality criteria and specifications, and that they are free of errors, omissions, or inconsistencies.
Identifying and correcting any defects or deviations in the project documents, and updating them accordingly.
Validating and approving the project documents, and obtaining the acceptance and sign-off from the stakeholders.
Document quality control is an important aspect of project quality management, as it helps to ensure the clarity, reliability, and usability of the project information, and to avoid any confusion, misunderstanding, or miscommunication among the project team and the stakeholders.
In this question, the project manager is managing a technical project that requires intensive documentation as part of the key deliverables. In a project review meeting, a key stakeholder reports that the latest documentation provided by the project manager includes a reference to unrelated products. This indicates that the project manager has not performed document quality control properly, and that the project documents are not accurate, complete, or consistent. This can create problems for the project manager and the project team, such as rework, delays, disputes, or dissatisfaction. To resolve this issue, the project manager should take the following action:
Develop a standard for document quality control. The project manager should establish and document the quality criteria and specifications for the project documents, and communicate them to the project team and the stakeholders. The project manager should also define and implement the document quality control processes and procedures, such as review, inspection, correction, validation, and approval. The project manager should also assign roles and responsibilities for document quality control, and provide the necessary tools and resources. The project manager should also monitor and measure the document quality performance, and identify and implement any improvements. This will help to ensure the quality and consistency of the project documents, and to meet the expectations and needs of the stakeholders.
The other options are not correct because they do not provide a valid way to resolve the issue of document quality control. Option A is wrong because it suggests that the project manager should ask the project management office (PMO) to support and review all deliverables, without developing a standard for document quality control. This would be delegating the responsibility and accountability for document quality control to the PMO, and not addressing the root cause of the issue. Option B is wrong because it implies that the project manager should log the issue in the risk register and the issue log, without developing a standard for document quality control. This would be documenting the issue and its impact, but not taking any corrective or preventive actions to resolve it. Option D is wrong because it assumes that the project manager should assign a technical writer to the project, without developing a standard fordocument quality control. This would be adding a resource to the project, but not defining or communicating the quality criteria and specifications for the project documents. References:
PMBOK Guide, 6th edition, pages 286-287, 318-319, 374-375
Project Quality Control - ProjectEngineer
The Quality Management Plan in Project Management
Project Quality Management According to the PMBOK - ProjectEngineer