Presentation on theme: "Change Control Change is inevitable - how to manage it?"— Presentation transcript:
Change Control Change is inevitable - how to manage it?
Risks and Change Unforeseen problems Other proposed changes Didn’t happen Solved within project as defined Assess proposed change - accept or reject RISKS What might happen RISKS What might happen ISSUES What has happened ISSUES What has happened CHANGE What needs to be done CHANGE What needs to be done
Examples of Change a change in external customer requirements an internal change driven from the top down, for example, in response to a change in the business philosophy a modification (improvement) identified by a team member a risk materialising (e.g. a competitor gaining a foothold in the market much sooner than expected) a change in the economic climate an omission, mistake or inaccurate estimate in original proposal
The Nature of Change impact on cost (increase or decrease) impact on schedule (delays or acceleration) impact on project deliverable impact on benefits (increase or decrease)
Approval & Authorisation
Change Management and Control System Change Management and Control System Recognise all Change Requests Enter into Change Request Progress Log Assess impact - especially on Cost and Schedule Take decision or refer to appropriate authority Inform all interested parties (including reasons if rejected) Implement the change (if it is accepted) Update all documentation
Change Control Process DEFINITION What is a Scope Change Environment, Modifications, Faults, etc Prepare & Submit Change Request Form Record change in the Change Request Progress Log Review change request and assess impact Amend as appropriate Conditional Yes Is change accepted? No Yes Obtain Financial Authorisation (if required) Yes Record in Change Request Progress Log Implement Change Update Project Documentation Inform interested parties Record decision in Change Request Progress Log Inform Interested Parties Is change authorised? Conditional Yes