Correct order for submitting the Change request

Submitted by dpng on Tue, 11/02/2010 - 16:28

As I go through mock exam questions in preparation for my imminent test I am just getting confused on things that I thought were clear. I’m finding the explanations to different questions explain  different responses to essentially the same situation.  Here is one situation on which I would appreciate advice. The question is an amalgamation of several questions to bring out the relevant options , and I don’t know the true answer since I have seen at least 3 different answers provided as the correct answer. Or of course if there is some other scenario that should occur in place of these options, what is it?

Thanks.

Question: You are nearing completion of the project when the customer requests you (PMgr) to add a new feature that is additional to the approved Scope. What does the Project Manager do first?

a.       He documents the change in a Change Request as per the Project Management plan and then analyses the impact.

b.      He analyses the impact on the triple constraints (Scope, Time, cost) and then he documents the change in a Change Request.

c.      He analyses the impact on the triple constraints and also on the project quality objectives and quality planning, and  then he documents the change in a Change Request.

d.     He requests the Customer to complete and submit a Change request.

Forums: 
PMP / CAPM exam Question bank
  • Log in to post comments
  • 2219 reads
admin's picture

admin

Wed, 11/03/2010 - 05:31

Well this questions is tricky in the sense it focuses on micro details. Basically the answer you choose has to be in the context of question and the given choices.


In my opinion first the customer has to submit the formal change request and give exact requirements. Once this is done, the project team will do the analysis and find the impact on the project's triple constraints. After that they will discuss the schedule, cost estimates with customer.


In some cases there will be a change control board who will approve / reject changes. The approval is usually done once the project team presents the impact to project's triple constraints.


Some times the CCB can also reject the change based on the change description and impact analysis would not have to be done. It totally depends on what process is agreed upon.


Hope this clarifies the flow. if you understand the concepts there is no need to worry about the right answer, once you glance through the options you will know which one is right. :)


 


 

Arif Kamran

Wed, 11/03/2010 - 09:54

whenever the change or additional feature is added to the scope it will be document for change request through PICC process (integration process). after that through this process to see the impact of this on other processes (triple constraints) for taking decision to continue with this change or just stop now. (always note down the risks involve by change or add additional feature).


i think this information will help you.


Arif Kamran  

bpp9614

Wed, 11/03/2010 - 16:03

He documents the change in a Change Request as per the Project Management plan and then analyses the impact.


Can customer create the Change Request (CR): I have never seen that practically. Generally the PM fills out the CR forms. Also he can do so by using tools like ClearQuest, which customer doesnt have access. Option 2 and 3 are tricky just to avoid. Generally without a CR number (e.g CR0001001), PM doesnt do an impact analysis formally.

interservicio

Wed, 03/12/2014 - 10:12

Sorry for "necroposting".

I do revive this old thread for some additional questions:

1.- AFAIK the PM shoudl evaluate the impact of the change not only in the 3 constraints but also looking in quality, HR, risks....

2.- A customer CAN make formal change requests by themself (as any other Stakeholder). i found it odd that the PM should do this process.

 

Therefore i think the best answer is D.