Did you know Cybrary's video training is FREE? Join more than 2,500,000 IT and cyber security professionals, students, career changers, and more, growing their careers on Cybrary.
This lesson focuses on performing integrated change control. This is the process of taking care of change requests. Performing integrated change control creates the approved change requests, change log, and project management plan. The inputs are the project management plan, work performance reports and change requests. The tools used are meetings, change request tools and expert judgement. [toggle_content title="Transcript"] The next process is perform integrated change control. This is the process while your change requests are going to and your main output is your approved change request. Perform integrated change control creates the approved change request. You also have a change log and you are going to have project management plan updates. The inputs are the project management plan, work performance reports and change request. The tools that are used are meetings, change request tools and expert judgement. Looking at this...what you are getting out of it is approved change request. These are requests that have been brought to this process, there is going to be a board, could be the sponsor, could be several people. They are going to go over this change request and they are either approve it or deny it or ask for more information. If they approve it, the output is obviously approved change request. The other output of this is you are going to have a change logs. You might have like an excel spread sheet and you are going to capture all these change requests. You might put a number on it like 001 all the way up to how many change requests you have. You are going to give a status report whether it is approved, denied, need more information or you are going to table it for another board meeting. If you do have approved changes, you will have to go back to your project management plan. This is the analysis, You are going to figure out what knowledge area this affects and then you update what sub plan that is. Say, I have something go wrong with the project; it didn't go with my baseline. It's going to affect the time. So I have to go back to my time and affect my schedule to show that it is going to have an impact of say two weeks, or That can also have an effect on cost. Then I will have to go to the cost knowledge area and affect my cost baseline to say "now it is going to cost us two weeks, it is going to cost us money as well", so its going to be an extra thousand dollars to get this done. The inputs are the project management plan, which we've talked about. So that's the main thing that we've created, the main document. Work performance reports, these are the more formalized reports. Obviously there is change request because you are trying to approve them. The tools that are used are meetings. You can set up meetings like bi weekly or monthly or however often we need to review changes. Change request tools, so that's basically tools to help facilitate, review and communicate what these changes are and expert judgement. Just have the expertise in this area to help with the process. Understanding what changes could occur, how it affects the project and where it affects all the other knowledge areas. so you're getting some good piece of information, performing integrated change control, determine what changes have been done and what needs to be done. Review and approve the change requests, monitor and adjust the baseline. You are going to have a time baseline, a cost baseline, quality baseline, scope baseline. Communicate the status of the project regarding the implemented changes. If you approve a change, the rest of the project team needs to notice and the sponsor needs to notice or stakeholders. You don't just want to approve a change request and not let anybody know. [/toggle_content]