#Perform Integrated Change Control (PICC) Process for PMP Exam - By SN Panigrahi, Essenpee Business Solutions, PMP, PMI, Perform Integrated Change Control (PICC), Change, Change Management, Change Management System, Change Management Control, Baseline, Change Request, Change Log, Change Control Board, Approved Change Request

1. 1

2. 2
Change is inevitable in any Project. Within your project, you will experience
change at some point.
Change is never easy, especially in a context of Managing Projects, as it
affects a lot of aspects. In order to ensure a smooth transition from the current
state to the desired state in projects, you need the correct change management
tools and resources at hand.
Having a well thought out plan on how to handle change when it is requested is
critical to your success.
Change Management is necessary to successfully implement changes in the
Project.
Change management has become one of the most critical success factors for
any Project and therefore "Change management is key to the project.“

3. 3
What is Change Management?
In the simplest of terms, change management is a systematic approach towards dealing with
change. It’s a structured way of applying tools, knowledge, and resources to effectively drive and
ensuring that changes are thoroughly and smoothly implemented, and that the lasting benefits of
change are achieved.
The underlying principle is that change does not happen in Isolation – it may impact the whole
Project, particularly on Six Constraints namely Scope, Schedule, Cost, Quality, Resources & Risk, as
the Project move from the Current Situation to the New one. Change Management is, therefore, a
very broad field, and approaches to managing change vary widely, from project to project.
For every project you should create a well thought out change management plan, because as we
said above, change is inevitable, so we have to plan for it.
Change management is a part of the Integration Management knowledge area and contains
processes within the Planning and Monitor and Control process groups.

4. 4
The change Management process is the sequence of steps or activities that a change
management team or project leader follow to apply change management to a change in order
to drive individual transitions and ensure the project meets its intended outcomes.
The below elements have been identified from research as key elements of a successful
change management process.
The activities involved in managing change can include:
➢ Is there is clear expression of the Reasons for Change
➢ “Why are we Making this change?”
➢ How big is this change?
➢ “What is Impact on Scope, Schedule, Cost, Quality, Resources & Risk due to Proposed
Changes?
➢ What are the Root Causes of Change?
➢ What Planning Activities Needed to Address the Impacts of the Change.
➢ “Who are the Sponsors we need to involve to make this successful?”
➢ How to implement the Changes

5. 5
➢ A Change Request is a Formal Proposal to modify any document, deliverable or baseline.
➢ Several Project Management Processes may Involve a Change Request.
➢ Changes may or may not impact the project baselines - sometimes only the performance
against the baseline is affected. Decisions on those changes are usually made by the project
manager.
➢ Change Requests that have an impact on the project baselines should be approved by the
CCB (if it exists) and by the customer or sponsor, unless they are part of the CCB.
➢ Change requests may include corrective action, preventive action, defect repairs, as well as
updates to formally controlled documents or deliverables to reflect modified or additional ideas or
content.
➢ Following are Change Management Activities :
❖ Identify changes. Identifying and selecting a change item for processes or project documents.
❖ Document changes. Documenting the change into a proper change request.
❖ Decide on changes. Reviewing the changes; approving, rejecting, deferring, or making any
other decision about changes to the project documents, deliverables, or baselines.
❖ Track changes. Verifying that the changes are registered, assessed, approved, and tracked
and communicating final results to stakeholders.

6. 6
Change
Request
Changes may or may not
impact the project baselines—
sometimes only the
performance against the
baseline is affected. Decisions
on those changes are usually
made by the project manager.
Change Requests that have an
impact on the project baselines
should be approved by the CCB
(if it exists) and by the customer
or sponsor, unless they are part
of the CCB.
Identify
Change
Document
Changes
Decide on
Changes
Track
Changes
Corrective Action
Preventive Action
Defect Repairs
May Include
Updates
A Change Request is a
Formal Proposal to modify
any document, deliverable
or baseline.
Several Project
Management Processes
may Involve a Change
Request.

7. 7
➢ Many Processes Produce Change Requests as an output.
➢ The Perform Integrated Change Control Process is conducted from Project Start through
Completion.
➢ It is the ultimate Responsibility of the Project Manager.
➢ Change Requests can Impact the Project Scope and the Product scope, as well as any
Project Management Plan (Baselines – Scope, Schedule, Cost) component or any Project
Document.
➢ Changes may be Requested by any Stakeholder involved with the project and may occur at
any time throughout the project life cycle.
➢ Before the Baselines are established, changes are not required to be formally controlled
by the Perform Integrated Change Control process.
➢ Once the Project is Baselined, change requests go through this process.
➢ As a general rule, each project’s configuration management plan should define which project
artifacts need to be placed under configuration control. Any change in a configuration
element should be formally controlled and will require a change request.

8. 8
❖ Although changes may be initiated verbally, they should be Recorded in Written Form and
entered into the change management and/or configuration management system.
❖ Change Requests may require information on estimated schedule impacts and estimated
cost impacts prior to approval.
❖ Whenever a change request may impact any of the project baselines, a formal integrated
change control process is always required.
❖ Every documented change request needs to be either approved, deferred, or rejected by a
responsible individual, usually the project sponsor or project manager.
❖ The Responsible Individual will be identified in the project management plan or by
organizational procedures.
❖ When required, the Perform Integrated Change Control process includes a change control
board (CCB), which is a formally chartered group responsible for reviewing, evaluating,
approving, deferring, or rejecting changes to the project and for recording and
communicating such decisions.
❖ Only approved changes should be incorporated into a revised baseline.

9. 9
❖ A Change Request (CR) is an Output of most Executing and all M&C Processes.
❖ A CR is an Input (only) to the PICC Process.
❖ A Decision for CR is taken by the Change Control Board (CCB) in PICC process.
❖ A CR can be Approved, Partially Approved, Rejected, or kept in abeyance by CCB.
❖ Approved changes and Change Log is Output of PICCC.
❖ Only Approved Changes should be incorporated into a Revised Baseline.
❖ Approved changes are Input to the Direct & Manage Project Work (D&MPW) process,
where they are Implemented after Updating the Project Management Plan (Mainly
Baselines – Scope Baseline, Schedule Baseline, Cost Baseline) & Project Documents.

10. 10
Process
Perform
Integrated
Change
Control
(PICC)
is the process
of Reviewing all
Change
Requests &
Deciding on
Change.
Process Group
Monitor & Control
Knowledge Area
Integration
Management
Input
Change Requests
Executing
Processes
Monitor &
Control
Processes
Output
Direct &
Manage
Project Work
Change Log
Approved
Change
Requests
Many Processes
Produce Change
Requests as an Output. Control
Quality
Control
Procurement

11. 11
Identify New Change Request
Impact Analysis of CR
Document CR
Present / Submit CR to the
CCB
Decision to Accept or Reject
CR
Update Change Log, Project Mgt
Plan & other Documents +
Communicate to Stakeholder(s)
Implement Approved
Changes
A CR can be Identified by Any Stakeholder.
She/he can be part of project team or
outside the project team.
PM and/or Project Team members analyze
the impact of CR on various project
objectives e.g. Scope, Schedule, Cost etc.
PM and/or Project Team members
documents the CR. They also document
suggested alternatives and possible
solutions.
PM and/or Project Team members presents
the documented CR to CCB members. They
explain its impact on various project
objectives.
CCB takes a decision on CR. It can approve,
reject, or partially approve the CR. It can
also ask PM to re-document it or postpone
the decision to a later date.
PM and/or Project Team members Update
Project Plan & Documents and
communicates the decision taken by CCB to
the Concerned stakeholders.
PM and/or Project Team members
implement the approved changes
Any Stakeholder
Project Manager
Project Manager
Project Manager
PM could be a Member of CCB
Change Control Board
(CCB)
Project Manager
Project Manager

12. Whether
Change is
Required?
Changes Requested by
Many Stakeholders
Changes may be
Required from Various
Process
Reject Change
Yes
No
Raise
Change Request
Record Change Request in
Change Log
Analyse Impact of
Change Request
Submit Change Request
with the Proposal to CCB
CCB has
Authority to
Accept or
Reject the
Change
Request
Change
Request
Accepted by
CCB?
Update Change Log;
Update Project Mgt. Plan;
- Update Baselines
Update Project Documents
Communicate to
Concerned Stakeholders
Approved Change Request
Yes
Update Change Log;
Communicate to
Initiator
After Updates
Implement Changes
as per the Revised Project
Management Plan &
Project Documents
Direct & Manage
Project Work
Control
Quality
No
Control
Procurement
Execute

13. 13
➢A modification to any formally controlled deliverable, project management plan component, or
project document.Change
❖Change Management is a systematic approach towards dealing with change. It’s a structured way
of applying tools, knowledge, and resources to effectively drive and ensuring that changes are
thoroughly and smoothly implemented, and that the lasting benefits of change are achieved.
Change
Management
➢A Component of the Project Management Plan that establishes the change control board,
documents the extent of its authority, and describes how the change control system will be
implemented.
Change
Management Plan
❖A Process whereby Modifications to Documents, Deliverables, or Baselines Associated with the
Project are Identified, Documented, Approved, or Rejected.
Change
Control
➢Perform Integrated Change Control (PICC) is the process of Reviewing all Change Requests &
Deciding on Change.
Perform Integrated
Change Control
(PICC)

14. 14
❖The approved version of a work product that can be changed only through formal change control
procedures and is used as a basis for comparison to actual results.Baseline
➢A Formal Proposal to Modify a Document, Deliverable, or Baseline. This request is submitted to the
Change Control Board.Change Request
❖A comprehensive list of changes submitted during the project and their current status.Change Log
➢A formally chartered group responsible for reviewing, evaluating, approving, delaying, or rejecting
changes to the project, and for recording and communicating such decisions.
• The CCB should be Created during the Planning Process Group.
Change Control
Board (CCB)
❖Approved change requests are an output of the Perform Integrated Change Control process, and
include those requests reviewed and approved for implementation by the project manager or by the
change control board (CCB) when applicable.
Approved Change
Requests

15. 15

16. 16
Question:
Before the baselines of your IT development project are established, the
project sponsor requires a major change in the project. You assessed him on
the impacts that change would have in the project. Which of the following
statements is true about this situation?
A. That change does not have to be formally controlled by the
Perform Integrated Change Control process.
B. Any change in a configuration element should be formally
controlled and will require a change request.
C. Formal integrated change control process is always required.
D. That change must be communicated to all stakeholders previously.

17. 17
Answer : A
Once the project is baselined, change requests go through this process.
As a general rule, each project’s configuration management plan should
define which project artifacts need to be placed under configuration
control. Any change in a configuration element should be formally
controlled and will require a change request.
But this is not the case since the baselines are not yet established.
Before the baselines are established, changes are not required to be
formally controlled by the Perform Integrated Change Control
process. Therefore, the right choice for this question is A. [PMBOK 6th
edition, Page 115] [Project Integration Management]

18. 18
Question :
You have just received a change from customer. Customer has
analysed that it does not impact the schedule and easy to implement.
What should you do first?
A. Request Permission from Project Sponsor
B. Send the Change to Change Control Board for Approval
C. Implement the Change as soon as Possible
D. Ask the Customer to Raise Change Request & then
Evaluate the impact on the project

19. 19
Answer : D
Look at the basic principles and change management process to analyze the question. Basic principles
says it is only project team that should do impact analysis. Customer analysis is not required and not
sufficient. Irrespective of customer has done the analysis or not, project team must do impact analysis. Let’s
analyze the options:
A - Request permission from project sponsor: You need permission from change control board
to implement a change and not from sponsor.
B - Send the change to change control board for approval: If you look at the change
management process, you can send the change request to change control board only after
impact analysis. Customer impact analysis is neither valid not sufficient.
C - Implement the change as soon as possible: If you follow the process, you can implement a
change request only after CCB approval.
D - Ask the Customer to Raise Change Request & then Evaluate the impact on the
project: You should evaluate the impact i.e. do impact analysis. So the answer is D. A question
may arise how we can do impact analysis when a formal change request is not created and not
gone through qualification test yet as per process. The answer is, these two steps are not
available in the options. If either of them was available, I would have chosen it. We have to
choose best out of available options.
So the answer is D.

20. 20
You are a member of Change Control Board (CCB) where you can
approve or reject change requests. A change request has been
rejected by CCB, it means that change request will not be added to
scope of work. In case of rejection of a change request, which of
following document is updated?
A. Issue log
B. Change log
C. Project Management Plan
D. Requirements traceability matrix
Ans: B.
All change requests whether approved or rejected must be recorded in the
change log.

21. 21
Question :
You are developing an application. In the last week, you have made the first
delivery to your customer. Looking at the delivery, your customer has requested
a change in the application and customer ask you to urgently respond on the
change What is the BEST way for you to handle it?
A. Analyze the impact of the change on the project
B. Immediately ask your team to start work on the change and
meanwhile you will do the impact analysis and take the approval from
change control board
C. Create a formal change request
D. Call a team meeting to decide next step

22. 22
Answer : C
A- Analyze the impact of the change on the project: You should analyze the impact of the change on the
project but let us see if there is any option in B, C or D that comes before this step.
B- Immediately ask your team to start work on the change and meanwhile you will do the impact analysis
and take the approval from change control board: Asking your team to immediately start working on the
change will be a total violation of change management process and also dangerous for you as you do not
know the impact. By start working without understanding impact, you probably delay it instead of delivering
it early.
C- Create a Formal Change Request: Yes, you should first create a formal change request. This should
be preferred over A as it comes first in the Integrated Change Control Process.
D- Call a team meeting to decide next step: Calling a team meeting to decide next step shows that you
either do not have a change management process or you do not have inclination to follow it or you are
unaware of it. If you have a change management process, next step is defined there, just follow it, there is
no need to call a meeting.
So the answer is C as it is preferred over A.

23. 23
A. Get the list of changes from the customer and ask your team to work on the changes
immediately
B. Schedule a call with customer and tell the customer that all requirements have been
fulfilled as per the scope of the project and hence changes cannot be made
C. Ask the customer to file a change request
D. Estimate cost and time needed to finish the suggested changes and get it approved by
the customer
You are a project manager working in IT industry, your team is working on a
web application which is in user acceptance phase. You are satisfied the
project is ahead of schedule. Your customer suggests some changes in the
deliverables. The changes requested by the customer are minor and can be
accomplished within the deadline. What you should do next?
Answer : C.
All changes have to go through the Change Control Board (CCB).

24. 24
Question
Your project is half way. It is running on time and within budget. A team
member comes to you and informs that he has added an Extra Features to
the Project Scope that customer would like. The Customer and Team
Member do not want to Raise Change Request since there is no impact on
time and cost. What should be your NEXT step after hearing this
information?
A. Send this information to change control board to take a decision
B. Issue a change request and get it approved as soon as possible
C. Instruct the team member to remove the extra functionality
D. Present it to the customer as a value add

25. 25
Answer : C
A- Send this information to change control board to take a decision: It is not right as this is not
correct change control process. You should send the change request to CCB only when we have
completed impact analysis.
B- Issue a change request and get it approved as soon as possible: Change request is to be issued
before implementation of change and not after its implementation. It is violation of the process.
C- Instruct the team member to remove the extra functionality : You can instruct the team
member to remove it as it is not in the scope. Adding an extra feature which is not in
the scope is called Gold Platting and not required at all.
D- Present it to the customer as a value add: Presenting it as value add is not only violation of
Integrated Change Control Process but also risky as it was implemented without the knowledge of
customer.
So the answer is C. Explain to your team member that he/she is not expected to work on features out of
scope and ask him/her to remove it.

26. 26

27. 27
https://www.youtube.com/channel/UCVZ
ScNa_leR8XbYINEwTFwQ/videos

28. 28

29. Contact Details:
SN Panigrahi
9652571117
snpanigrahi1963@gmail.com
29