Requirements Management

Correct Answer: Stop further project activities, review the impact, update the requirements accordingly to meet the quality standards and then re-plan the project.

The best course of action in a case where a significant quality standards oversight has taken place during an infrastructure project would be to 'Stop further project activities, review the impact, update the requirements accordingly to meet the quality standards and then re-plan the project.' This brings us to the wrong options and why: - 'Continue the project as it is, to keep the project on schedule.' This answer is incorrect because it suggests ignoring the quality standards oversight which could potentially lead to serious incidents or failures in the project - 'Add a new quality standard control in the project without changing the already completed work' - This action might be a good measure, but it doesn't address the oversights that have already occurred. There's a risk that the completed work that doesn't meet the quality standards may have to be reworked or may lead to issues in future - 'Change the quality standards to match the completed work.' This suggests altering the quality standards to match the already completed work, which is unethical and could compromise the safety, functionality, and longevity of the project So, the proper procedure would be to halt the project activities, reevaluate the extent of the oversight, update the requirements to meet the quality standards, and then, plan the remaining project activities accordingly.

Correct Answer: Evaluate the impact of the added requirements on the project's scope, time, and cost, then discuss it with stakeholders.

The best action plan for a project manager when additional requirements are added after the planning phase is to evaluate the impact of these changes on the project's scope, time, and cost and then discuss these impacts with the stakeholders. This is because any change in the project requirements can have potential implications on the project timeline, cost and other resources which can significantly affect the overall project delivery. Ignoring the requirements or accepting them all without analyzing the impacts, as suggested in the other answers, can lead to unexpected issues or project failures. Equally, incorporating changes into the project without consulting stakeholders is not a good practice in project management as it can lead to misunderstandings or dissatisfaction among the stakeholders.

Correct Answer: Negotiate with stakeholders to prioritize key requirements and relegate 'Nice-to-Have' requirements in the backlog for consideration only if time and resources allow.

As a project manager, it's essential to balance stakeholder's expectations with what's achievable given the project constraints including time, cost, and resources. The best approach when dealing with 'Nice-to-Have' requirements, which are typically not critical for the project, is to negotiate with stakeholders in order to prioritize key requirements while relegating 'Nice-to-Have' requirements in the backlog. These can be considered if time and resources allow, ensuring that the project does not get delayed due to these lower-priority features. The other approaches such as including all 'Nice-To-Have' requirements regardless of the impact on the project timeline or resources could potentially endanger the successful execution of the project, while ignoring them or demanding stakeholders to eliminate all 'Nice-to-Have' requirements might lead to dissatisfaction among stakeholders