Change requests

Change requests

Below are the description of all the uses of the working document “Change requests”:

“Change Requests” is an output for the process “Direct and Manage Project Work “.
A change request is a formal proposal to modify any document, deliverable, or baseline. An approved change request will replace the associated document, deliverable, or baseline and may result in an update to other parts of the project management plan. When issues are found while project work is being performed, change requests are submitted, which may modify project policies or procedures, project scope, project cost or budget, project schedule, or project quality. Other change requests cover the needed preventive or corrective actions to forestall negative impact later in the project. Requests for a change can be direct or indirect, externally or internally initiated,
and can be optional or legally/contractually mandated, and may include: – Corrective action?An intentional activity that realigns the performance of the project work with the
project management plan;
– Preventive action?An intentional activity that ensures the future performance of the project work is
aligned with the project management plan;
– Defect repair?An intentional activity to modify a nonconforming product or product component; and/or – Updates?Changes to formally controlled project documents, plans, etc., to reflect modified or additional ideas or content.

“Change Requests” is an output for the process “Monitor and Control Project Work “.
As a result of comparing planned results to actual results, change requests may be issued to expand, adjust, or reduce project scope, product scope, or quality requirements and schedule or cost baselines. Change requests may necessitate the collection and documentation of new requirements. Changes can impact the project management plan, project documents, or product deliverables. Changes that meet the project?s change control criteria should go through the integrated change control process established for the project. Changes may include, but are not limited
to, the following: – Corrective action?An intentional activity that realigns the performance of the project work with the
project management plan;
– Preventive action?An intentional activity that ensures the future performance of the project work is
aligned with the project management plan; and – Defect repair?An intentional activity to modify a nonconforming product or product component.

“Change Requests” is an input for the process “Perform Integrated Change Control”.
All of the Monitoring and Controlling processes and many of the Executing processes produce change requests as an output. Change requests may include corrective action, preventive action, and defect repairs. However, corrective and preventive actions do not normally affect the project baselines?only the performance against the baselines.

“Change Requests” is an output for the process “Validate Scope”.
The completed deliverables that have not been formally accepted are documented, along with the reasons for nonacceptance of those deliverables. Those deliverables may require a change request for defect repair. The change requests are processed for review and disposition through the Perform Integrated Change Control process

“Change Requests” is an output for the process “Control Scope”.
Analysis of scope performance can result in a change request to the scope baseline or other components of the project management plan. Change requests can include preventive or corrective actions, defect repairs, or enhancement requests. Change requests are processed for review and disposition according to the Perform Integrated Change Control process.

“Change Requests” is an output for the process “Control Schedule”.
Schedule variance analysis, along with review of progress reports, results of performance measures, and modifications to the project scope or project schedule may result in change requests to the schedule baseline, scope baseline, and/or other components of the project management plan. Change requests are processed for review and disposition through the Perform Integrated Change Control process. Preventive actions may include recommended changes to eliminate or reduce the probability of negative schedule variances.

“Change Requests” is an output for the process “Control costs”.
Analysis of project performance may result in a change request to the cost baseline or other components of the project management plan. Change requests may include preventive or corrective actions, and are processed for review and disposition through the Perform Integrated Change Control process.

“Change Requests” is an output for the process “Perform Quality assurance”.
Change requests are created and used as input into the Perform Integrated Change Control process to allow full consideration of the recommended improvements. Change requests are used to take corrective action, preventive action, or to perform defect repair.

“Change Requests” is an output for the process “Control Quality “.
If the recommended corrective or preventive actions or a defect repair requires a change to the project management plan, a change request should be initiated in accordance with the defined Perform Integrated Change Control process.

“Change Requests” is an output for the process “Manage project team”.
Staffing changes, whether by choice or by uncontrollable events, can affect the rest of the project management plan. When staffing issues disrupt the project team from adhering to the project management plan such as causing the schedule to be extended or the budget to be exceeded, a change request can be processed through the Perform Integrated Change Control process. Staffing changes may include moving people to different assignments, outsourcing some of the work, and replacing team members who leave.
Preventive actions are those actions that are developed to reduce the probability and/or impact of problems before they occur. These actions may include cross training to reduce problems during project team member absences and additional role clarification to ensure all responsibilities are fulfilled.

“Change Requests” is an output for the process “Control communications “.
The Control Communications process often results in the need for adjustment, action, and intervention. As a result, change requests will be generated as an output. These change requests are
processed through the Perform Integrated Change Control process and may result in: – New or revised cost estimates, activity sequences, schedule dates, resource requirements, and analysis
of risk response alternatives;
– Adjustments to the project management plan and documents;
– Recommendations of corrective actions that may bring the expected future performance of the project
back in line with the project management plan; and – Recommendations of preventive actions that may reduce the probability of incurring future negative project performance.

“Change Requests” is an output for the process “Control Risks”.
Implementing contingency plans or workarounds sometimes results in a change request. Change requests are prepared and submitted to the Perform Integrated Change Control process. Change requests can
include recommended corrective and preventive actions as well.
– R ecommended corrective actions. These are activities that realign the performance of the project work with the project management plan. They include contingency plans and workarounds. The latter are responses that were not initially planned, but are required to deal with emerging risks that were
previously unidentified or accepted passively.
– R ecommended preventive actions. These are activities that ensure that future performance of the project work is aligned with the project management plan.

“Change Requests” is an output for the process “Plan Procurement management”.
A decision that involves procuring goods, services, or resources typically requires a change request. Other decisions during procurement planning can also create the need for additional change requests. Change requests are processed for review and disposition through the Perform Integrated Change Control process.
Changes to the project management plan, its subsidiary plans, and other components may result in change requests that impact procurement actions. Change requests are processed for review and disposition through the Perform Integrated Change Control process.

“Change Requests” is an output for the process “Conduct Procurements “.
Change requests to the project management plan, its subsidiary plans, and other components are processed for review and disposition through the Perform Integrated Change Control process.

“Change Requests” is an output for the process “Control Procurements “.
Change requests to the project management plan, its subsidiary plans, and other components, such as the cost baseline, schedule baseline, and procurement management plan, may result from the Control Procurements process. Change requests are processed for review and approval through the Perform Integrated Change Control process.
Requested but unresolved changes can include direction provided by the buyer or actions taken by the seller, which the other party considers a constructive change to the contract. Since any of these constructive changes may be disputed by one party and can lead to a claim against the other party, such changes are uniquely identified and documented by project correspondence.

“Change Requests” is an output for the process “Manage Stakeholder Engagement”.
Managing stakeholder engagement may result in a change request to the product or the project. It may also include corrective or preventive actions to the project itself or to the interaction with the impacted stakeholders, as appropriate.

“Change Requests” is an output for the process “Control Stakeholder Engagement”.
Analysis of project performance and interactions with stakeholders often generates change requests. These
change requests are processed through the Perform Integrated Change Control process as follows: – Recommended corrective actions include changes that bring the expected future performance of the
project in line with the project management plan; and – Recommended preventive actions can reduce the probability of incurring future negative project performance.

This definition was found in the PMBOK V5

Go back to the Glossary or to the Mapping

Leave a Reply

Your email address will not be published.