Declined Change Request Documentation and Storage
Question
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?
Answers
Explanations
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 question.
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 to be fleshed into the project documents, but the declined changes are part of the change request log.
As a project manager, one of your key responsibilities is to manage changes to the project scope and ensure that these changes do not adversely affect the project's objectives, timeline, budget, or quality. In some cases, you may need to decline a proposed change request due to the risks associated with it.
To document and store the declined change request, you should use the change request log. The change request log is a document that contains information about all change requests submitted for the project, including their status, priority, impact, and disposition.
When you decline a change request due to risk, you should include the reason for the decision in the change request log. This will ensure that all stakeholders are aware of the decision and the reason behind it, which will help to prevent similar requests in the future.
It is important to note that while the declined change request should be documented and stored in the change request log, it should not be included in the project document updates. Project document updates should only reflect approved changes that have been implemented in the project, not those that have been declined.
The project archives and lessons learned are also important documents for project management, but they are not the appropriate places to store a declined change request. The project archives are used to store historical project documents and records, while lessons learned capture insights and recommendations for future projects based on the successes and challenges of the current project.
