Scribd
Upload
728 views1 page

Project Change Request Process

The document outlines the project management knowledge areas and processes. It discusses the key responsibilities within each process, including planning, execution, monitoring and controlling. It then provides details on the change request process, noting that a Change Control Board is typically responsible for reviewing, evaluating, approving or rejecting change requests. The process involves updating project baselines and documentation if a change request is approved.

Uploaded by

yash shah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
728 views1 page

Project Change Request Process

The document outlines the project management knowledge areas and processes. It discusses the key responsibilities within each process, including planning, execution, monitoring and controlling. It then provides details on the change request process, noting that a Change Control Board is typically responsible for reviewing, evaluating, approving or rejecting change requests. The process involves updating project baselines and documentation if a change request is approved.

Uploaded by

yash shah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Knowledge Area Planning Execution Monitoring & Controlling

Project Integration Direct & Manage Project Monitor & Control Project
Management Works Work
Project Scope Validate Scope
Management Control Scope
Project Time
Control Schedule
Management
Project Cost
Control Cost
Management
Project Quality Perform QA
Control Quality
Management
Project HR Manage Project Team
Management
Project Comms.
Control Communications
Management
Project Risks
Control Risks
Management
Project Proc. Plan Procurements Conduct Procurements
Control procurements
Management
Project SH. Manage Stakeholder Engage Control Stakeholder
Management Engage

Output is

CHANGE REQUESTS

1. Assess CR and try minimizing impact on Project Objectives

2. Let the CR originator (Stakeholder) clearly understand


Manage SH
Impact to project objectives engagement

3. Formally document Change Request (CR) and enter to Change


Management / Configuration Management system
4. Enter to Change LOG

5. Perform Integrated Change Control

The Question is: Who is responsible for approve or Reject CR?

A. In General: An authority within the project management team.


B. By a responsible individual, usually the project sponsor or project manager.
C. By Change Control Board (CCB): which is a formally chartered group responsible for
reviewing, evaluating, approving, delaying, or rejecting changes to the project, and
for recording and communicating such decisions.
D. Project Sponsor or Customer ( final approval) unless they are part of CCB

IS CHANGE REQUESTS NO
APPROVED

YES
6. UPDATE Project Baselines
7. UPDATE Project Management Plan
8. UPDATE project Documents

9. Update Change
LOG

10. Communicate decisions to


Stakeholders (approve, reject,
delay,..)
11. Implement approved CR
Direct And Mange Project Work

12. Inspect Implementation of CR END


Control Quality (The Output is Validated Changes )

13. Validate Implementation of CR. (Validated Changes is input


to Monitor and Control Project Works)
** CR’s Require validation to ensure and confirm that the
changes were appropriately implemented and executed

NO YES Knowledge Area Planning Execution Monitoring & Controll

You might also like