In the Project Management Institute (PMI) framework, a change request is a formal proposal used to "process" modifications to an aspect of the project, whether related to budget, schedule, scope, or other elements.

Here is an overview of the process for handling change requests within a project:

Identification of the Need for Change

Any member of the project team can identify a need for change, whether due to an unexpected discovery, a revised client requirement, or other reasons.

Submission of the Request

Once a need for change is identified, it is submitted as a change request. This request must be clearly documented, detailing the nature of the required change, its impact on the project (in terms of schedule, costs, resources, etc.), and the reasons justifying the change.

Evaluation of the Request

The change request is evaluated by the project management team. This involves analyzing the change's impact on the project as a whole, considering constraints, objectives, and priorities.

Decision & Implementation

Based on the evaluation, a decision is made to approve or reject the change request. This decision is typically made by the project steering committee or another governance body defined in the organizational structure.

If the change request is approved, it is implemented within the project framework. This may involve adjustments to planning, resource allocation, budget, etc.

It should be noted that change requests, supported by a robust and fail-safe processing system, are indispensable for achieving project performance and maintaining its configuration for several reasons:

• Flexibility: Projects are often subject to changes and unforeseen events. Change requests enable adaptation to new circumstances while maintaining the project's relevance.

• Control: By formalizing change requests, project managers can better control project modifications, assess their impact, and make informed decisions regarding their implementation.

• Communication: Change requests also serve as a communication mechanism among project stakeholders. They facilitate the sharing of information about project developments and ensure that all parties understand the reasons and implications of proposed changes.

Change requests are thus a crucial element of project management, ensuring performance, flexibility, control, and effective communication in project execution.

According to the Project Management Institute (PMI), change requests can be categorized into three main types: corrective action, preventive action, and defect repair. Below is a detailed description of each category:

Corrective Action

• Description: A corrective action is a measure taken in response to an issue or deviation from project objectives. It aims to rectify an existing situation that could jeopardize the project's success.

• Objective: The primary objective of a corrective action is to bring the project back on track by addressing errors, gaps, or deviations from the initial project plan.

• Example: If a project task is delayed due to late delivery of a critical component, a corrective action might involve reallocating resources or revising the schedule to recover the delay and meet project deadlines.

Preventive Action

• Description: A preventive action is a proactive measure implemented to prevent a potential problem from occurring. It focuses on identifying and mitigating risks before they become actual issues for the project.

• Objective: The primary goal of a preventive action is to reduce risks and enhance project performance by anticipating and averting potential issues.

• Example: If a project faces risks related to upcoming regulatory changes, a preventive action could involve establishing regulatory monitoring and developing an adaptation plan to minimize the impact of these changes on the project.

Defect Repair

• Description: Defect repair involves correcting errors or anomalies identified in project deliverables. It ensures that the project's products or services meet quality standards and specified requirements.

• Objective: The main goal of defect repair is to ensure compliance and quality of project deliverables by resolving any identified defects or non-conformities.

• Example: If a software developed as part of a project contains bugs or features that do not work as intended, defect repair would involve fixing these issues to ensure the final product functions correctly and meets stakeholder expectations.

These three categories of change requests (corrective action, preventive action, and defect repair) as defined by PMI cover a wide range of situations in project management, providing solutions to address errors, prevent future issues, and ensure the quality of deliverables.

Frequent PMP® & CAPM® exam questions :

These practice questions are expertly designed by Examera specialists to deepen your understanding of key concepts and enhance your skills in tackling exam-style challenges. To unlock the full experience and gain access to unlimited real exam MCQs, log in to the Examera simulators and start practicing today!

When a change request is made, what is the first step to take in a project?
a) Implement the change immediately
b) Inform all stakeholders
c) Document the change request
d) Reject the request if it seems unnecessary
Correct answer: c) Documenting is the first step to ensure that the change request is clear and properly recorded before going through the evaluation and approval steps.

Who is responsible for approving or rejecting a change request in a project?
a) The project sponsor
b) The Change Control Board (CCB)
c) The project manager
d) The project team
Correct answer: b) The Change Control Board (CCB) is responsible for reviewing and deciding on change requests to ensure governance and alignment with project objectives.

What should the project manager do after a change request is approved?
a) Implement the change immediately
b) Update the stakeholder register
c) Revise the project management plans
d) Close the change request
Correct answer: c) The management plans must be updated to reflect the impacts of the approved change, ensuring alignment with the new project objectives.

Which document contains the detailed description of a change request?
a) The risk register
b) The change log
c) The change management plan
d) The requirements traceability matrix
Correct answer: b) The change log is used to record and track details, status, and decisions related to each change request.

What does a "deferred decision" mean in the change management process?
a) A request is temporarily rejected
b) A request is pending additional information
c) A request is approved but not yet implemented
d) A request is canceled
Correct answer: b) A deferred decision indicates that additional information is needed to make an informed decision on the request.

When can a change request be directly rejected by the project manager?
a) If it is deemed to have no impact on the project
b) If it exceeds the approved budget
c) If it is outside the project scope
d) If it is not documented
Correct answer: c) The project manager can immediately reject a request if it is out of scope, as it does not align with the validated project objectives.

Which process is used to analyze the potential impact of a change request?
a) Configuration management
b) Gap analysis
c) Impact analysis
d) Requirements review
Correct answer: c) Impact analysis assesses the possible effects of a change on scope, schedule, cost, and quality, helping to make informed decisions.

How does the project manager communicate the outcome of a change request?
a) Through a formal meeting only
b) By updating the stakeholder register
c) Through documented communication to relevant stakeholders
d) By informing only the sponsor
Correct answer: c) Documented communication ensures that all appropriate stakeholders are informed and that decisions are traceable.

A change request has been approved but not yet implemented. What should the project manager do?
a) Immediately begin implementation
b) Plan actions to integrate it into the project
c) Inform the CCB
d) Update the project charter
Correct answer: b) Planning is essential to integrate the change into existing processes while minimizing disruptions.

Which tool is used to track the status of change requests in a project?
a) The issue log
b) The stakeholder register
c) The change log
d) The project charter
Correct answer: c) The change log helps track and manage each request efficiently, including its current status and associated decisions.

Frequent PSM®, PSPO & ACP® exam questions :

These practice questions are expertly designed by Examera specialists to deepen your understanding of key concepts and enhance your skills in tackling exam-style challenges. To unlock the full experience and gain access to unlimited real exam MCQs, log in to the Examera simulators and start practicing today!

In a Scrum project, who is responsible for approving a change request?
a) Scrum Master
b) Product Owner
c) Development Team
d) Stakeholders
Correct answer b): The Product Owner approves change requests as they are responsible for managing the Product Backlog and ensuring changes align with the product vision and stakeholder needs.

What should be done if a critical change request is raised during a Sprint?
a) Immediately implement the change
b) Add the change to the current Sprint Backlog
c) Cancel the Sprint and start a new one
d) Add the change to the Product Backlog for prioritization
Correct answer d): Changes should be added to the Product Backlog to maintain Sprint focus. Critical changes can be prioritized for the next Sprint, ensuring minimal disruption to the team.

When can changes be introduced into a Scrum project?
a) Only at the start of a Sprint
b) Any time, but they must go through the Product Owner
c) Only during Sprint Review
d) Changes are not allowed once development starts
Correct answer b): Agile welcomes change, but the Product Owner ensures they are managed properly to maintain product focus and deliver value.

What is the primary tool for managing change requests in Scrum?
a) Change Log
b) Product Backlog
c) Sprint Backlog
d) Issue Tracker
Correct answer b): The Product Backlog is the central tool for managing all changes and requirements, allowing prioritization and alignment with the product goal.

If stakeholders request a major change during a Sprint, how should the Scrum Team respond?
a) Pause the Sprint to address the change
b) Reject the request
c) Inform stakeholders it will be evaluated after the Sprint
d) Add the change to the Sprint Backlog
Correct answer c): Changes are considered at the end of the Sprint to maintain focus and predictability. Stakeholders should be informed of the process to evaluate their request.

Who decides the priority of a change request in Scrum?
a) Development Team
b) Scrum Master
c) Product Owner
d) Stakeholders
Correct answer c): The Product Owner determines the priority of items in the Product Backlog, balancing stakeholder needs, technical constraints, and business value.

What happens if a high-priority change request is introduced late in a Sprint?
a) The Sprint is extended to complete the change
b) The Sprint is canceled
c) The change is added to the Product Backlog
d) The change is immediately implemented
Correct answer c): Late changes are added to the Product Backlog to be prioritized for future Sprints, keeping the current Sprint focused and predictable.

How should a change request that does not align with the product vision be handled?
a) Implement it as a low-priority task
b) Discuss with stakeholders and reject if necessary
c) Add it to the Sprint Backlog
d) Defer it indefinitely
Correct answer b): The Product Owner should discuss misaligned changes with stakeholders and reject those that do not contribute to the product vision, ensuring focus on valuable outcomes.

What is the role of the Scrum Master in handling change requests?
a) Approving changes
b) Implementing changes
c) Ensuring the process is followed
d) Prioritizing changes
Correct answer c): The Scrum Master ensures the Scrum framework is followed and that the team adheres to processes, but they do not make decisions about change requests.

What should be included in a change request to facilitate its evaluation?
a) Estimated cost and implementation time
b) Justification and expected impact
c) Detailed technical specifications
d) Stakeholder approval
Correct answer b): A change request should include its justification and expected impact to help the Product Owner and team assess its value and alignment with the product goals.