Project

Change Control
 What is Change Control?
A collection of policies, processes,
and procedures to manage changes
to baseline project processes and
deliverables.

A mandatory process that must be

followed in order to make a change
from baseline requirements.
Importance of a Change
Control Plan
• Controls project scope creep
• Helps keep project on schedule
• Helps keep project on budget
• Enhances Project communication
• Avoids developer ‘gold plating’
• Identifies requirements for future
project phases (deferred changes)
 Why Change Control?
• Because scope creep is lethal
• Because only fools believe you can
“freeze” requirements & then build to
them
• Because even though you all agree in
November doesn’t mean you’ll be
speaking in January
• Because all of the parameters of a
systems project can change overnight
Project Resources Triangle

Change
Scope Resources

Time
 Aspects of the Change
Control Plan
• Formal Change Control during all phases
• Requirements Phase
• Specifications Phase
• Testing Phase
• Conversion Phase
• Implementation Phase
• Requests made via the Change Request
Form
• Requests reviewed and approved by the
Change Control Board
Change Control Board
• Itemize here
 Change Control Process
• Submit a Change Request Form
• Perform Preliminary Analysis
• Change Control Board (CCB) review
• If approved:
• Perform detailed analysis
• Record all changes to requirements and
other deliverables
• Implement the approved change
 Formal Change Control
Process
Identify Change

Submit RFC
Request More
Information

Remove
Analysis CCB Review Reject RFC
duplicates

Action Required Put in later

(AR) Release

Input at later
time

Analyze in Detail
Document
& Implement
Changes
Change

Report back
to CCB

One or more AR's still

open
Followup

Close RFC

Communicate
Action Taken
 Project CHANGE REQUEST
USER NAME:

USER DEPARTMENT:

DATE:

Description of the change:

Justification:

For IT Use:
Impact on schedule, or
resources:

New or altered Requirement(s):

Disposition: (A)pproved or (R)ejected

Authorized by:

Authorized On:
 Team Members
Responsibilities
• Identify proposed changes
• Submit Change Request
• Perform impact analysis
• Implement changes
• Update all relevant
documentation
• Suggest process improvements
 Conclusion
• Effective change control is critical
to project success.
• All proposed changes are
reviewed and approved.
• Changes have an impact on cost,
schedule and/or quality.
• Deliverables are adjusted to
reflect approved changes.