Perform Integrated Change Control

Correct Answer: Request the stakeholders to formally submit the change requests.

When stakeholders request changes to the project scope, the first step should be to ask them to formally submit the change requests. This is crucial in maintaining a record of changes and ensuring each change is analyzed for its potential impact on the project. Jumping into implementing the changes immediately, as stated in one of the other answers, could lead to scope creep, cost overrun or project failure. Therefore, it is not the correct approach. Similarly, holding a Change Control Board (CCB) meeting immediately or using the Issue Log to resolve requests are not the appropriate initial steps. These actions come after a formal change request has been submitted and need to be evaluated.

Correct Answer: Implement the approved change

As a project manager, once a change request has been approved by the Change Control Board (CCB), it should be implemented. The CCB is a formally chartered group responsible for review, evaluation, approval or rejection of changes, with all decisions documented and communicated to stakeholders. Therefore, the correct action is to 'Implement the approved change'. The option to 'Resubmit the change request for further discussion' is incorrect. If the change has been approved by the Change Control Board, there is no need for further discussion The choice to 'Reject the change request and proceed as planned' is not appropriate as the decision to approve the change has already been made by the Change Control Board The option to 'Discuss the issue with the team member's functional manager' is also wrong because the functional manager does not have authority over the change control process. However, the project lead may want to address the team member’s concerns outside of the change control process.

Correct Answer: Evaluate the proposed feature for its potential impact on project constraints and submit it for change control process

The best course of action is to evaluate the proposed feature for its potential impact on project constraints and submit it for the change control process. As a project manager, it's important to carefully consider any proposed changes to the project scope, timeline, or deliverables. While the additional feature may improve user experience, it's crucial to assess how it would affect the project schedule, budget, and resources. By submitting the proposed change through the established change control process, the project manager ensures that the change is properly documented, evaluated, and approved by relevant stakeholders before implementation. This helps to maintain project control and reduces the risk of scope creep or schedule delays. The other options are not appropriate because they either ignore the stakeholder's input entirely, bypass the necessary change control procedures, or dismiss the suggestion outright without proper evaluation.