MONITOR & CONTROL
1
Focus is on Integrated Change Control
OBJECTIVES
Identify the purpose of integrated change control
Understand inputs, tools and techniques, and
outputs of integrated change control
2
WHERE ARE WE?
Initiation
Planning
Execution
Monitor and Control
Closing
3
QUESTIONS TO ASK DURING THIS PHASE
OF THE PROJECT?
How is the project progressing against Objectives?
Milestones? Schedule? Budget?
4
THINGS YOU WILL DO
Measure against the baseline
Determine Variances and return to schedule.
Meet Objectives.
Respond to threats and opportunities.
User the change control procedures you have
identified.
Leverage tools and techniques such as Earned
Value
Control procurement.
Configuration Management
Integrated Change Control
5
PROCESS
The next two slides describe the PMBOK 4th
Edition Processes that occur during this phase of
the game.
6
MONITORING & CONTROLLING PROCESSES
Integration
Scope
Monitor & Control
Project Work
Perform Integrated
Change Control
Verify Scope
Control Scope
Time
Control Schedule
Cost
Control Cost
7
Quality
Perform Quality
Control
1 of 2
MONITORING & CONTROLLING PROCESSES
(CONTD.)
2 of 2
Communications
Report Performance
Risk
Monitor & Control
Risks
Procurement
Administer
Procurements
8
WHAT IS CHANGE CONTROL?
Integrated
Change Control deals
with coordinating and
managing changes across the
entire project.
Identifying, documenting,
approving or rejecting, and
controlling changes to the
project baseline. (PMBOK)
9
WHY CHANGE CONTROL?
Change
is inevitable on any
project
Managing change well will
ensure success
Documentation is key: Example:
If
scope change was not
documented then “it was NOT
REQUESTED”.
10
CHANGE CONTROL
A change control system is a collection of formal,
documented procedures that defines how project
performance will be monitored and evaluated,
and includes steps by which official project
documents may be changed.
It includes:
Documentation
Tracking systems (PMIS)
Processes
Approval levels necessary for authorizing changes
11
CHANGE CONTROL BOARD
A
formally constituted group of
stakeholders responsible for
reviewing, evaluating, approving,
delaying, or rejecting changes to a
project, with all decisions and
recommendations being recorded.
PMBOK 4th Edition p. 428
12
CHANGE REQUEST:
ISSUES TO THINK ABOUT
Oral/Written
Direct/Indirect
Internal/External
Legal
• In what format was it sent?
• How was it requested?
• Where was it initiated?
• Contracts require formality
13
CHANGE CONTROL PROCESS
• Request
Submitted
Change
Analysis
Decision
• PM
• Change
Control Board
• Approved
• Not Approved
Communicate
Status
14
OUTCOME
No Change: No impact on the schedule or budget
Minor Change: Altered schedule; Additional time
and resources needed
Major change: Redefining the scope of the project
Multiple release versions, prioritizing
deliverables across release dates
Changing baseline
Communicate Status
15
SUMMARY: CHANGE CONTROL SYSTEM
A
collection of formal documented
procedures that define how project
deliverables and documentation will
be controlled, changed and approved.
In most applications areas, CCS is a
subset of the configuration
management system (CMS).
PMBOK 4th Edition p. 428
16
SUMMARY: CONFIGURATION
MANAGEMENT
Used to ensure the description of the project’s
product is correct and complete by applying
technical and administrative direction and
surveillance to:
The functional and physical characteristics of an item
or system
Control any changes to such characteristics
Record and report the change and its implementation
status
Audit the items and system to verify conformance to
requirements
17
SUMMARY: CONFIGURATION
MANAGEMENT SYSTEM (CMS)
Collection of formal documented procedures used
to apply technical and administrative direction
and surveillance to: identify and document the
functional and physical characteristics of a
product, result, service, or component; control
any changes to such characteristics; record and
report each change and its implementation
status; and support the audit of products, results,
or components to verify conformance to
requirements. It includes the documentation,
tracking systems, and defined approval levels
necessary for authorizing and controlling
changes.
PMBOK
4th Edition p. 428
18
WORKSHOP
Comment on the change control request in your
organization.
Identify the size of your project under discussion.
What works? What does not work?
Recommendations for improvements?
19
0
