CHANGE WORKFLOW. Is that correct?

After reviewing several q&a regarding this topic i came with this detailed workflow.

I would like to check with you if it's correct and detailed.

1.- Receive FORMAL request of change from stakeholder. (Some questions tell you that the request is informal, so you have to make the customer to send a formal request).

2.- EVALUATE the impact, regarding scope, time, cost, quality, risk, Resources... (anything else here?).

3.- INFORM the stakeholder regarding the impact of the change.

4.- Send the request to CHANGE COMITE BOARD and/or SPONSOR

5.- Implement the APPROVED change.

 

Is this correct?. Any other thoughs?

Regards,

Swapnyl's picture

1. Any communication with a PM has to be formal in a project unless it is from a team member

2. for point 4. it is Change Control Board CCB that approves all the CRs.

 

Thanks both of you ¡

You are close to a good format. I would edit as follows:

1.- Receive FORMAL request of change from stakeholder. (In PMI-land there can't be an 'informal' request for change).
2.- DOCUMENT the request in the CHANGE LOG.
3.- CONVENE and SUBMIT the request to the Change Control Board.
3.- EVALUATE the impact, regarding scope, time, cost, quality, risk, Resources... (simply put, any component of the project that could be affected by the change should be reviewed).
4.- UPDATE the PMP, CHANGE LOG, and any other relevant project documents.
5.- INFORM relevant stakeholders (team, customer, sponsor, etc) of the impact of the change.
6.- Implement the APPROVED change.

Feel free to contact me for more information. I teach for PMstudy.com and cover this thoroughly in class.
Sandra.s@PMstudy.com