Oliver 75 - 41st Question

[jyotimayank]

41. A change request in a project has been rejected some weeks ago. Yesterday, the project manager found out that it nevertheless has been implemented by the team members, who knew of the change request, but not of the rejection.
In order to avoid such a situation, rejected change requests should be consistently communicated to stakeholders through which process?

A. Report performance
B. Verify scope
C. Perform integrated change control
D. Monitor and control risks

[sarthy]

C , all the stakeholders must be communicated about approval/rejection of any CR

[Ananyapmp]

C, change requests comes under Perform Integrated changes.

[jyotimayank]

Yes the correct answer is C.

All change requests (rejected or approved) should be consistently communicated to all the stakeholders in a timely manner.

Whenever a change request is received or suggested or identified, it needs to be logged in the Change log of the project. Irrespective of the size of the change or the impact of the change, each and every change need to be logged in the change log. Project manager alone cannot do the impact analysis, inputs from the project team and if required, from stakeholders are needed. In impact analysis, the impact of the proposed change is analyzed on all project constraints like on scope, schedule, quality, risk, cost or any other project dimension. If Change request gets Rejected or Postponed, the communication is sent to request or / stakeholder with the reasons of rejection or postponed.

As per PMBOK® Guide 5th Edition

Change requests are subject to the process specified in the change control and configuration control systems. Every documented change request needs to be either approved or rejected by a responsible individual, usually the project sponsor or project manager. The responsible individual will be identified in the project management plan or by organizational procedures. When required, the Perform Integrated Change Control process includes a change control board (CCB), which is a formally chartered group responsible for reviewing, evaluating, approving, delaying, or rejecting changes to the project, and for recording and communicating such decisions.

Refer to Page 366-380 of PMBOK® Guide 5th Edition

For more insight of this topic refer to the following blog and webinar

Webinar on Integrated change management

http://www.izenbridge.com/videogallery/ ... zenbridge/

Blog: Integrated-change-control-sequence-of-change-request

http://www.izenbridge.com/blog/integrat ... e-request/