You work as a project manager for BlueWell Inc.
You have declined a proposed change request because of the risk associated with the proposed change request.
Where should the declined change request be documented and stored?
Click on the arrows to vote for the correct answer
A. B. C. D.A.
The change request log records the status of all change requests, approved or declined.
The change request log is used as an account for change requests and as a means of tracking their disposition on a current basis.
The change request log develops a measure of consistency into the change management process.
It encourages common inputs into the process and is a common estimation approach for all change requests.
As the log is an important component of project requirements, it should be readily available to the project team members responsible for project delivery.
It should be maintained in a file with read-only access to those who are not responsible for approving or disapproving project change requests.
Incorrect Answers: B: The project archive includes all project documentation and is created through the close project or phase process.
It is not the best choice for this option.
C: Lessons learned are not the correct place to document the status of a declined, or approved, change request.
D: The project document updates is not the best choice for this question.
It can be placed into the project documents, but the declined changes are part of the change request log.
As a project manager, it is your responsibility to manage changes in the project scope, budget, schedule, or other project aspects. When a proposed change request is declined due to associated risks, it is important to document and store the request for future reference. This documentation can help in identifying patterns or trends that may emerge from similar proposals.
The correct answer to this question is option A, i.e., the declined change request should be documented and stored in the change request log. The change request log is a project document that tracks all the changes made to the project scope, schedule, budget, or other project aspects. It includes information about the requester, the change request description, the justification for the change, and the status of the request.
When a change request is declined, it is important to document the reasons for the rejection and store it in the change request log. This documentation can help in keeping a record of all proposed changes, their disposition, and the reasons behind the decision.
Option B, i.e., project archives, refers to the storage of project-related documents after the project has been completed. The declined change request is not a project deliverable, and hence, it does not belong in project archives.
Option C, i.e., lessons learned, refers to the process of capturing knowledge gained during a project to improve future projects. Although the declined change request can be used to identify potential risks, it is not a lesson learned as it does not provide information about what worked or did not work well in the project.
Option D, i.e., project document updates, refers to updating project documents such as the project management plan, project charter, or other project documents. Although the declined change request may require updates to these documents, it is not the correct answer as it does not directly address the question of where the declined change request should be documented and stored.
In conclusion, the correct answer to the question is option A, and the declined change request should be documented and stored in the change request log.