You are on page 1of 4

4.

5 Perform Integrated Change Control


4.5.1.1 Project Management Plan
Changes are requested against "approved" baselines in the Project Management Pla
n. The Project Management Plan also describes the change management process.
Pg 97
4.5 Perform Integrated Change Control
4.5.1.1 Project Management Plan
Changes are requested against "approved" baselines in the Project Management Pla
n. The Project Management Plan also describes the change management process.
Pg 97
4.5 Perform Integrated Change Control
4.5.1.2 Work Performance Reports
Reports on resource availability, schedule, cost and earned value can be used fo
r decision-making by the Change Control Board.
Pg 97
4.5 Perform Integrated Change Control
4.5.1.3 Change Requests
All change requests must be processed through the integrated change control proc
ess. Change requests may include corrective actions, preventive actions, defect
repairs, and updates to project plans and documentation.
Pg 97
4.5 Perform Integrated Change Control
4.5.1.3 Change Requests
All change requests must be processed through the integrated change control proc
ess. Change requests may include corrective actions, preventive actions, defect
repairs, and updates to project plans and documentation.
Pg 97
4.5 Perform Integrated Change Control
4.5.1.4 Enterprise Environmental Factors
The main EEF that may be used in the integrated change control process is the Co
nfiguration Management System, which is a subsystem of the overall Project Manag
ement Information System (PMIS). It manages the functional and physical characte
ristics of products, services or results, controls changes to the those items, a
nd supports their audit to verify conformance to requirements.
Pg 98
4.5 Perform Integrated Change Control
4.5.1.4 Enterprise Environmental Factors
The main EEF that may be used in the integrated change control process is the Co
nfiguration Management System, which is a subsystem of the overall Project Manag
ement Information System (PMIS). It manages the functional and physical characte
ristics of products, services or results, controls changes to the those items, a
nd supports their audit to verify conformance to requirements.
Pg 98
4.5 Perform Integrated Change Control
4.5.1.4 Enterprise Environmental Factors
The main EEF that may be used in the integrated change control process is the Co
nfiguration Management System, which is a subsystem of the overall Project Manag
ement Information System (PMIS). It manages the functional and physical characte
ristics of products, services or results, controls changes to the those items, a
nd supports their audit to verify conformance to requirements.
Pg 98
4.5 Perform Integrated Change Control
4.5.1.5 Organizational Process Assets
Procedures for change control and authorizations, and configuration management k
nowledge base (which provides the latest version of all project plans and docume
nts) may be used in this process.
Pg 98
4.5 Perform Integrated Change Control
4.5.1.5 Organizational Process Assets
Procedures for change control and authorizations, and configuration management k
nowledge base (which provides the latest version of all project plans and docume
nts) may be used in this process.
Pg 98
4.5 Perform Integrated Change Control
4.5.1.5 Organizational Process Assets
Procedures for change control and authorizations, and configuration management k
nowledge base (which provides the latest version of all project plans and docume
nts) may be used in this process.
Pg 98
4.5 Perform Integrated Change Control
4.5.2.2 Meetings
Special meetings, known as change control meetings, are used by the Change Contr
ol Board (CCB) to review and disposition (approve or reject) change requests.
Pg 99
4.5 Perform Integrated Change Control
4.5.2.2 Meetings
Special meetings, known as change control meetings, are used by the Change Contr
ol Board (CCB) to review and disposition (approve or reject) change requests.
Pg 99
4.5 Perform Integrated Change Control
4.5.2.3 Change Control Tools
Manual or automated tools may be used for configuration and change management. T
hese tools can help to manage change requests and communicate their status to th
e appropriate stakeholders.
Pg 99
4.5 Perform Integrated Change Control
4.5.2.3 Change Control Tools
Manual or automated tools may be used for configuration and change management. T
hese tools can help to manage change requests and communicate their status to th
e appropriate stakeholders.
Pg 99
4.5 Perform Integrated Change Control
4.5.3.1 Approved Change Requests
The change requests that have been processed through the Perform Integrated Chan
ge Control process and approved, are known as Approved Change Requests. Approved
change requests are implemented through the Direct and Manage Work process.
Pg 99
4.5 Perform Integrated Change Control
4.5.3.2 Change Log
Status of all change requests, accepted or rejected, is updated in the Change Lo
g.
Pg 100
4.5 Perform Integrated Change Control
4.5.3.3 Project Management Plan Updates
Approval of change requests may necessitate updates to project baselines and sub
sidiary project management plans, both of which are part of the Project Manageme
nt Plan.
Pg 100
4.5 Perform Integrated Change Control
4.5.3.4 Project Documents Updates
Any project document that is under formal change control may get revised as part
of the Perform Integrated Change Control process.
Pg 100
4.6 Close Project or Phase
The process of finalizing all activities across all of the Project Management Pr
ocess Groups to formally complete a project or phase.
Pg 100
4.6 Close Project or Phase
4.6.1.1 Project Management Plan
The project management plan specifies the project completion requirements.
Pg 102
4.6 Close Project or Phase
4.6.1.1 Project Management Plan
The project management plan specifies the project completion requirements.
Pg 102
4.6 Close Project or Phase
4.6.1.2 Accepted Deliverables
Accepted deliverables are the deliverables that meet the acceptance criteria, an
d have been formally signed off by the customer through the Validate Scope proce
ss. These deliverables are transitioned or handed-off to the customer in the for
m of final product, service or result.
Pg 102
4.6 Close Project or Phase
4.6.1.2 Accepted Deliverables
Accepted deliverables are the deliverables that meet the acceptance criteria, an
d have been formally signed off by the customer through the Validate Scope proce
ss. These deliverables are transitioned or handed-off to the customer in the for
m of final product, service or result.
Pg 102
4.6 Close Project or Phase
4.6.1.3 Organizational Process Assets
OPAs such as closure guidelines or requirements (e.g., project audits, project e
valuations, and transition criteria) may be used in the Close Project or Phase p
rocess.
Pg 102
4.6 Close Project or Phase
4.6.1.3 Organizational Process Assets
OPAs such as closure guidelines or requirements (e.g., project audits, project e
valuations, and transition criteria) may be used in the Close Project or Phase p
rocess.
Pg 102
4.6 Close Project or Phase
4.6.2.1 Expert Judgment
Project management expertise may be required to ensure that project closure stan
dards and guidelines are followed. Technical expertise may be required to hand-o
ff completed deliverables to the customer or the next phase of the project.
Pg 102
4.6 Close Project or Phase
4.6.2.2 Analytical Techniques
Regression Analysis and Trend Analysis can be applied during Project Closure. Fo
r example, Regression Analysis can be performed to determine how long it would t
ake to scale up the new system (delivered by the project) to full capacity.
Pg 103
4.6 Close Project or Phase
4.6.2.3 Meetings
Lessons learned, project closeout, user group, and review meetings may be conduc
ted at project closeout.
Pg 103
4.6 Close Project or Phase
4.6.3.1 Final Product, Service or Result Transition
The deliverables of the project are handed-off to the customer or transferred to
the next phase of the project.
Pg 103
4.6 Close Project or Phase
4.6.3.2 Organizational Process Assets Updates
Project plans, files, closure documents (such as customer sign-off on the delive
rables and the project as a whole), and historical information (issues, risks, b
est practices, lessons learned, etc.) are archived for reference on future proje
cts.
Pg 103
4.6 Close Project or Phase
4.6.3.2 Organizational Process Assets Updates
Project plans, files, closure documents (such as customer sign-off on the delive
rables and the project as a whole), and historical information (issues, risks, b
est practices, lessons learned, etc.) are archived for reference on future proje
cts.
Pg 103
5.1 Plan Scope Management
The process of creating a scope management plan that documents how the project s
cope will be defined, validated, and controlled.
Pg 107
Restricted Account: Access is limited to ITTO Secrets of Integration Management
processes. Premium subscribers can view all 618 ITTO Secrets.
Restricted Account: Access is limited to ITTO Secrets of Integration Management
processes. Premium subscribers can view all 618 ITTO Secrets.
Restricted Account: Access is limited to ITTO Secrets of Integration Management
processes. Premium subscribers can view all 618 ITTO Secrets.
Restricted Account: Access is limited to ITTO Secrets of Integration Management
processes. Premium subscribers can view all 618 ITTO Secrets.
Restricted Account: Access is limited to ITTO Secrets of Integration Management
processes. Premium subscribers can view all 618 ITTO Secrets.
Restricted Account: Access is limited to ITTO Secrets of Integration Management
processes. Premium subscribers can view all 618 ITTO Secrets.
Restricted Account: Access is limited to ITTO Secrets of Integration Management
processes. Premium subscribers can view all 618 ITTO Secrets.