process of making change_doubt

Submitted by BK on Fri, 05/17/2013 - 08:28

I am little confused for process of making changes..

here is the steps what I got:

 

Process of Making Changes:

1. Prevent the root cause for changes

2. Identify change

3. Look at impact of the change

4. Create a change request

5. Perform Inetegrated Change Control

                            a. evaluate the impact

                            b. create options - are created based on crashing, fast tracking, reestimating..etc

                            c. get change request approved internally

                            d. get customer buy-in (if required)

6. Adjust the Proj Mgmt Plan, proj doc, baseline

7. Communicate change to stakeholders

8. Manage Project to the revised Proj mgmt Plan.

 

Now I am little confused between point 3 and 5.a both are talking about evaluating..then what is the difference?

Some detail explaination needed.

 

Forums: 
PMP Exam Tips, Tricks and Lessons Learnt.
  • Log in to post comments
  • 556 reads
admin's picture

admin

Sat, 05/18/2013 - 04:59

 This is an FAQ, please search on PMZIlla 

http://pmzilla.com/sequence-steps-regarding-issues-or-change-requests

 

http://pmzilla.com/pmp-question-change-request-processing-sequence

cnppmp's picture

cnppmp

Sat, 05/18/2013 - 05:44

The above details are from RM.


Point3: I think it talks about the evaluation doen by the project management team, to assess the impact at their level and submitting the change request. There could be soem cases where project maanger implement the change if none of constraints are getting impacted but it still goes the Control management system process.


Point5: If at all the change request gets submitted , it's again the Change control board member to do their evaluation and take the final step of accepting or rejecting. They have lot more responsibility and separate gorup of stakeholder or member looking at it.


This is what I could make out from the reading of RM notes.


Regards


CN Patil


 

BK

Sat, 05/18/2013 - 07:24

 Thanks..How about below steps for making changes? that I prepared from different sources.

Lemme know ur thought.

 

·       

Evaluate and assess the changes. Determine how the changes are going to have an impact on the project.

• create option: Discuss with team members how best to handle the changes (is it possible to crash, fast- track, etc.?). Also, try to determine what would be the implication of each change – e.g., impact on scope, schedule, cost, quality, etc.

• Inform customer about the implication of the changes.

• If customer still wants the changes to be implemented, discuss with the management, sponsor, and other stakeholders.

• Based on their inputs, if the change is warranted, a change control request will have to be formally made and entered into the change management/configuration management system, necessary approvals need to be received, and then the team will work on the approved changes.

·       

Update status of the change in change control system

·       

Adjust proj mng plan, baseline, proj doc

·       

Mng sh expectation by communicating the change to SH affected by change.