Change Control in Integrated Change Control
I have seen such detailed explanations, especially by the PM PrepCast team, that I am sending my first post. Hope I get a detailed explanation as others.
I have just started my PMP and am looking at the Project Integration Management Knowledge Area. I am getting confused with the entire end-to-end change control process. For example:
1) Lets assume Change Requests get created in the Control Scope/Control Schedule etc process. I do understand that change requests are inputs to the the Perform Integrated Change Control which are approved/rejected by the CCB and then they act as an input to Direct and manage project execution as "Approved Change Requests". But I see that that the Direct and Manage Project Executon process as well as the Control Scope/Schedule process both have Project Management Plan/Project Document updates as their output which confuses me.
2) Some books mention that a change request needs to be created first and then impact analysis done with options while others say that impact analysis should be done with options and then a change request should be created.
Could someone kindly give a detailed explanation of the entire change process anatomy from start to end i.e. from inception of change to communication the information to the stakeholders once a change gets approved?