(1.6) Integrated Change Control
(1.6.1) Process Input
... generated by predecessor processes
- Project Management Plan
- Requested Changes
- generated by:
- Monitor and Control Project Work
- Direct and Manage Project Execution
- Scope Definition
- Create WBS
- Scope Verification
- Scope Control
- Activity Definition
- Activity Sequencing
- Activity Resource Estimating
- Schedule Developement
- Schedule Control
- Cost Estimating
- Cost Budgeting
- Cost Control
- Perform Quality Assurance
- Perform Quality Control
- Manage Project Team
- Information Distribution
- Performance Reporting
- Risk Monitoring and Control
- Plan Purchases and Acquisitions
- Select Sellers
- Contract Administration
- generated by:
- Work Performance information
- generated by: Direct and Manage Project Execution
- Recommended Preventive Actions
- Recommended Corrective Actions
- Recommended Defect Repair
- Deliverables
- generated by:
... introduced by external units
- Enterprise Environmental Factors
- Organizational Process Assets
(1.6.2) Process Definition
Integrated Change Control is the process for "[...] reviewing all change requestes, approving changes, and controlling changes to the deliverables and organizational assets" (comp. PMBOK3, p. 79)
- Part of the Monitoring and Controlling Process Group
- Father process of the following child processes, which also use the input and generate or modify the output of this process
- Scope Control
- Schedule Control
- Cost Control
- Member of Knowledge Area Project Integration Management
(1.6.3) Tools and Techniques
PMBOK Mentioned Methods
- Project management methodology deliveres methods and processes "[...] that aids a project management team in implementing Integrated Change Control for the project"
- Project management information system is "an automated system" being used by the project management team as "an aid for implementing an Integrated Change Control process for the project, facilitating feedback for the project and controlling changes across the project"
- Expert judgement is used by collecting experts into the change control board
(comp. PMBOK3, p. 99)
Open Source Tools
- NN
(1.6.4) Process Output
- Approved Change Requests should be (planned and) executed
- Rejected Change Requests should be monitored and controlled
- Updates of the Project Management Plan
- Updates of the Project Scope Statement
- Approved Corrective Actions should be (planned and) executed
- Approved Preventive Actions should be (planned and) executed
- Approved Defect Repair should be (planned and) executed
- Validated Defect Repair should be (planned and) executed
- Deliverables should be formally given to the project owner / sponsor before closing the project
(comp. PMBOK3, p. 99)
(1.6.5) Output Using Successor Processes
Successors using the output as own input(1):
- Scope Planning
- Scope Definition
- Contract Administration
- Create Work Breakdown Structure
- Activity Definition
- Activity Sequencing
- Activity Resource Estimating
- Activity Duration Estimating
- Schedule Development
- Cost Estimating
- Cost Budgeting
- Quality Planning
- Communications Planning
- Risk Management Planning
- Risk Identification
- Qualitative Risk Analysis
- Quantitative Risk Analysis
- Plan Purchases and Acquisitions
- Direct and Manage Project Execution
- Perform Quality Assurance
- Close Project
- Monitor and Control Project Work
- Scope Verification
- Scope Control
- Schedule Control
- Cost Control
- Perform Quality Control
- Performance Reporting
- Risk Monitoring and Control
- In this case we don't distinguish between successors using the initial generated output and successors using the updated output an input. We assume that approved change requests are generally generated by successor (sub-) processes and that they constitute backward lopps. (For details see FAQ::Q001)