Subtitles of the Movie

In this movie, we will review the workbook questions relating to the Integrated Change Control Process found within your work files. There are ten questions for review. The first question is what is the purpose of this process? The purpose of the Integrated Change Control Process is to review change requests, approve or deny them and control changes to the deliverables. You'll get this reminder in nearly every process review when requested changes appear as outputs and that's often. All requested changes are submitted into this process. Questions two, three and four ask you to recall the inputs, tools and techniques and outputs of this process. I'd like to draw your attention to input number two, requested changes. This is the only process where you'll see requested changes as an input. Other processes may have approved changes up here as an input after the Integrated Change Control Process generates them as an output. Question five states when in the project's lifecycle is this process performed? And the answer is throughout the entire project. We'll review the fact that changes must be submitted into the Change Control Process so often that it'd be nearly impossible to forget. And this is because this process deals with changes and necessary changes service regularly. The next question, question number six, states name at least five change activities that this process includes. There are actually eleven items that you could have chosen from, so I'll quickly mention them. These include identifying necessary and occurring changes, only approved changes take place, reviewing, approving requested changes, managing approved changes, maintaining baseline integrity, reviewing, approving recommended corrective and preventive actions, controlling or updating scope, cost budget, schedule and quality requirements based on approved changes, integrate approved changes, document the impact of changes, validate defect repair and control project quality based on reports. Let's move on to question seven, which says what are the objectives of the Configuration Management System in relation to this process. As you'll notice, the Configuration Management System is of course active throughout the project and it supports the different knowledge areas. In this case we're focused on how the Configuration Management System deals with changes. There are three objectives in relation to changes and these are it establishes an evolutionary method to identify and request changes to existing baselines that is consistent and then assess the value and effectiveness of these changes, provides opportunity to continuously validate and improve the project by looking at the impact of the changes and provides a solid way for the project management team to communicate changes to stakeholders. Still on the subject of the Configuration Management System, question eight now asks you for the Configuration Management System activities in relation to changes. This involves three things; configuration identification, configuration status accounting and configuration verification and auditing. Remember that this process is responsible for evaluating changes before making a decision. Let me give you a few more refresher details on these three items. Configuration identification provides basis for identifying, verifying, documenting and labeling of the configuration products and where changes are managed and accountability maintained. Configuration accounting captures, stores and accesses the configuration information that's necessary to manage products and product information effectively, and configuration verification and auditing make sure that the deliverables meet the requirements as defined in the configuration documentation. Question nine asks what is the name of the group that is responsible for approving or rejecting requested changes. And this one's fairly easy. The answer is Change Control Board. Question ten is a follow up to number nine. It asks who makes up the group referenced in the previous question. And the answer is that it varies by company and project. But for the most part, the Change Control Board is made up of stakeholders, the customer, project sponsor and sometimes also the project manager. And that covers all workbook questions for this section. As I mentioned earlier, you'll come across the Integrated Change Control Process more often than not within the processes, given that most projects are dynamic and therefore change continuously as being managed.