Exam PMP All QuestionsBrowse all questions from this exam
Question 292

A project is ready to deliver the first batch of the product when a quality control check rejects the product as unfit for delivery. The root cause analysis (RCA) shows that a component added as part of the latest change request was not tested throughout the development cycle.

What should the project manager do next?

    Correct Answer: A

    The project manager should review the change control process to ensure quality management artifacts are updated as part of the change. The root cause analysis indicated that the issue stemmed from a change request that was not properly tested. By addressing the change control process, the project manager can ensure that any future changes will be adequately documented and tested, which directly addresses the problem identified. This approach will help prevent similar issues from occurring in the future by ensuring changes are appropriately managed and quality control is maintained.

Discussion
FyrusOption: B

What to do NEXT Option A, which suggests reviewing the change control process, is important but is not the primary concern in this situation. The issue is related to quality management, specifically the testing of components. Quality Management Process Review: Given that the root cause of the issue is related to the quality of the product, it's crucial to review the quality management process. This involves examining how quality is planned, executed, and controlled throughout the project. Process Audit: Performing a process audit as part of ongoing quality assurance allows the project manager to identify weaknesses or gaps in the quality management process. It helps ensure that processes are being followed as intended and that all necessary steps, including testing of components added via change requests, are included.

JNLigondeOption: A

Shouldn’t it be A? We already know the process failed since the product was rejected. An audit is not the first thing that should be required. The issue occurred because of the change, so the change processes should be reviewed to ensure everything is accounted for next time.

aishOption: A

The root cause analysis highlighted that a component added as part of a change request was not tested throughout the development cycle. This suggests that the issue may have been related to the change control process not adequately ensuring that quality management artifacts, such as updated test cases, were consistently applied during the introduction of changes.

aishOption: B

Option A ("Review the change control process to ensure quality management artifacts are updated as part of the change") is focused on the change control process specifically. While it's important to ensure that quality management artifacts are updated with changes, this approach might not address broader quality management process issues.

SteAleOption: B

The RCA showed that the issue was caused by not having the CR tested. The testing process and approach should be defined as part of the quality management process

MartinussantikaOption: B

B is more comprehensive answer

ompkOption: B

B is more direct approach. as per A statement, why to go back to Change management process and looking at the updated or to make sure the new component is in the artifact ( documents etc). This doesn't fixes the problem. secondly the question is what should the PM do next ( the next immediate step) so B is more proactive as the new component was not tested so the "Audit" will provide the reason why the new component was not tested by QA.

RezaeeOption: A

A. Review the change control process to ensure quality management artifacts are updated as part of the change.

Bruce_LiuOption: A

A is more immediate and critical and specific to the current issue. B is not wrong but should only consider B after finishing A.

josephsafiranOption: A

The project manager should A. Review the change control process to ensure quality management artifacts are updated as part of the change. This issue arose due to a change request, so it’s important to review the change control process to ensure that all changes, including their potential impacts on quality, are properly documented and managed. This can help prevent similar issues in the future. However, the project manager should also consider the specific circumstances and dynamics of the project and the team when deciding on the best course of action

Uncle_LuciferOption: A

ensuring quality artifacts are checked will force quality test.

Lucky_CindyOption: B

B is correct

Only12goOption: A

Option A directly addresses the issue by reviewing the change control process to ensure that any changes (such as the introduction of a new component) lead to the necessary updates in quality management artifacts. This means making sure that when changes are made, they are properly reflected in test cases, quality checks, and other relevant documentation or processes.

adingmakiOption: A

HOW DO YOU EVEN KNOW IF THE QUALITY MANAGEMENT PLAN IS UPDATED OR NOT IF YOU ARE NOT GOING TO CHECK IT FIRST!? THIS IS A COMMON SENSE QUESTION.

khaleghiOption: B

selected answer:B option B does offer a comprehensive approach to address the issue. It ensures that not only is the particular problem tackled, but any potential weaknesses in the overall quality management process are also identified and addressed.

victory108Option: A

A. Review the change control process to ensure quality management artifacts are updated as part of the change

sassy2023Option: A

I think A is the first thing to do, aligning approved changes to quality assurance artifact.