3. Overview
• Change Control
– Purpose
– Project Issue Management
– Issue and Change Control procedure
– Change Budget
– Integrity of change
– Management
3
4. Change Control - Purpose
• Change in a project is highly likely
• All project change should be managed - as a formal Project
Issue
• Control of change means assessment of:
– impact of potential change
– importance
– cost
• Approved changes must be reflected in project documentation
4
5. Project Issue Management
The objective is to capture, log
and categorise all Project Issues,
these may be raised at any time
during the project, by anyone
with an interest in the project or
its outcome.
5
6. What could a Project Issue be?
• A change of requirements, however minor
• A change in the environment applicable to the project
• A problem occurring or being identified that was not
anticipated during risk analysis
• An anticipated but unavoidable risk occurring
• A problem or error occurring in work completed or currently
under way
• Advice of a new risk
• A query about any aspect of the project
6
7. Managing Project Issues will involve:
• Capturing and formally logging the Project Issue (in the Issue Log)
• Assessing the Project Issue to decide on the type and therefore
what action is required
• Investigating the required actions
• Documenting the actions and confirming their completion
• Reviewing the Issue Log on a regular basis to monitor progress
on outstanding Project Issues.
7
8.
9. Change Budget
– As well as considering where authority lies, the Project
Board must consider:
• How will changes be funded?
• Will the Project Board go back to corporate or programme
management to vary funding, timetable or scope each time a
change is desired?
9
10. Integrity of Change
• Project Issues should not be considered in isolation
– Benefit/Business Case driven
– The Risk Log
– Time/cost/risk function balance
Change
Risks
Cost
Time
Advantage
Saving
– Where the project is part of a programme.
10
11. Management
Project Managers should constantly be
looking for ways to take advantage of events
to improve on project costs, schedule or
performance.
These should be recorded as Project Issues
(and the final outcome should be recorded in
the Lessons Learnt Log)
11