Project Integration Management: Change Control vs Configuration Control for PMP Exam
One of the vital element for project management success is to control changes as in the Perform Integrated Change Control process, otherwise scope creep and missed requirements may result. Change management in projects involve Change Control and Configuration Control. These two terms are often used interchangeably in daily work, however, PMBOK® Guide has put specific meaning to each of them that Aspirants should not get confused.
Change Control and Configuration Control
- Change Control: In project management, change control is the process to identify, document, approve/reject and communicate changes to the baselines of the project (project baselines include scope, schedule, cost and other relevant baselines as required by the project management plan).
- The exact steps of change control is specified in the Change Management Plan by using the Change Control System.
- Changes need to be proposed in written form as Change Requests which will be studied, analyzed and approved/rejected by the relevant authorities.
- Change Control ensures all changes to the project are authorized which prevents scope creep and gold plating.
- Configuration Control: In project management, configuration control is about managing the specifications of the deliverables and processes with appropriate documentation throughout the lifecycle of the project from the very beginning to the closure of the project.
- The project configuration provides the information of the latest version of all the approved product and related documents/components and an archive of all previous versions.
- All the items under Configuration Control are known as Configuration Items (CI).
- Configuration Control is facilitated by the Configuration Control System.
- The exact details of Configuration Management is documented in the Configuration Control Plan, which is a subsidiary of the Project Management Plan.
- Configuration Management activities usually include:
- configuration identification
- configuration status accounting
- configuration verification / audit to ensure the latest configuration is adopted and delivered
The PMIS (Project Management Information System) is a tool that facilitates both the Configuration Control System as well as the Change Control System.
Mock Exam Question
- It was near the end of a software development project when the developer suddenly discovered that they had developed a feature based on an outdated component from the previous step. Rework was needed to correct the problem. Which of the following might not be performed well that would be the cause of the issue?
- Earned Value Control
- Configuration Control
- Change Control
- Project Control
Configuration Control is implemented to ensure the information of the latest versions of the software, specifications, etc. are to be available to the project team. If a feature is developed based on an outdated component, it is highly possible that the Configuration Control documents have not been updated timely.
Both the Change Control and Configuration Control processes aim to protect the project from :
- Change Control is about protecting the project from undocumented changes to the project baselines by addition/changing requirements, etc.
- Configuration Control is about managing the specifications/versions of the deliverables, processes and related documents throughout the lifecycle of the project.