The steps to perform integrated change control. Identify the need for change or that a change has already occurred on the project. Understand the root cause, the impact of the change on project objectives, or any needed adjustments to cost, time, scope, quality, risks, or resources. Create a formal change request and submit to the Change Control Board, which is intended to balance the needs of all stakeholders. Perform integrated change control by weighing all the options available and making a decision that's best for the project outcome.
Update the project management plan, the change log, and any related project documents. Implement the approved change into the project work and ensure the team understands the new work instructions. Manage stakeholder expectations by utilizing the change log to proactively communicate the change to stakeholders.
Monitor the project performance after the change is made and report to stakeholders if the change had the desired effect on the project. Change control is important, but the PM's real priority is to minimize the need for change in the first place. And we do that by first identifying the correct project approach and effectively collecting all the requirements. So change control is easier if you correctly select between a waterfall or agile approach at the beginning of the project. A waterfall approach means that a plan is in place at the beginning of the project, change is not generally desired, and change is integrated across the project.
An agile approach means that the plan is iteratively developed, change is expected and embraced, and change is managed within each iteration or sprint.