1957086Contract and Project ManagementDavid Sowden, The University of Hull
1957086Contract and Project ManagementChange Control techniquesDavid Sowden, The University of Hull
Overview• Change Control techniques – Important Points – Change Control steps – Prioritise – Impact analysis – Authorisati...
Important points –If a product is to be changed, its Product  Description should be checked for any necessary  changes –On...
Change control, steps• Changes can be: – A request to change what the project is set to deliver, For example,   the specif...
Change          New               issuecontrol,steps           Log                                Issue Log               ...
Prioritise• As well as the MOSCOW Method, one can also use: – A must - the final product will not work without this change...
Impact analysis – What would have to change, including any changes to linked   products – What effort the change would nee...
Authorisation – Only the Project Board or its delegated change authority should   make decisions on Requests for Change – ...
TASKHave issues within your     project been  fully documented?
Upcoming SlideShare
Loading in …5
×

57086 19 change_controltechniques

188 views

Published on

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
188
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

57086 19 change_controltechniques

  1. 1. 1957086Contract and Project ManagementDavid Sowden, The University of Hull
  2. 2. 1957086Contract and Project ManagementChange Control techniquesDavid Sowden, The University of Hull
  3. 3. Overview• Change Control techniques – Important Points – Change Control steps – Prioritise – Impact analysis – Authorisation 3
  4. 4. Important points –If a product is to be changed, its Product Description should be checked for any necessary changes –Once a product haas been approved, the Project Manager should not authorise any work that would change it without the approval of the Project Board 4
  5. 5. Change control, steps• Changes can be: – A request to change what the project is set to deliver, For example, the specification of requirements (Request for Change) – A suggestion to improve one or more of the project’s products (Request for Change) – A record of some current or forecast failure to meet a requirement (Off-Specification) 5
  6. 6. Change New issuecontrol,steps Log Issue Log Feedback to author Impact analysis Re- evaluate priority Within Y Taking Corrective tolerance? Action N Escalating Project Issues Pending Exception Implement Report Authoring Escalating Reject Exception a Stage or Project Giving Plan Exception Issues Remove Ad Hoc Plan cause Direction 6
  7. 7. Prioritise• As well as the MOSCOW Method, one can also use: – A must - the final product will not work without this change – An important change - its absence would be very inconvenient, although a work-around us possible for a while – A nice-to-have but not vital – A cosmetic change - of no importance – This does not involve a change 7
  8. 8. Impact analysis – What would have to change, including any changes to linked products – What effort the change would need – What the impact on the Team, Stage and Project Plans would be – Whether the impact would cause deviation beyond team, stage and project tolerances – What the impact on the Business Case would be – What the impact on the risks would be. Questions 8
  9. 9. Authorisation – Only the Project Board or its delegated change authority should make decisions on Requests for Change – For Off-Specifications, the Project Manager may try to solve the problem within stage tolerance margins. • Where this is not possible the exception procedure will be followed – After impact analysis Project Issues are passed to the Project Board/ change authority. – Project Issues are returned to the Project Manager, the Issue Log updated ann an updated copy sent to the author. – Any Project Issues whose implementation would cause deviation beyond stage or project tolerances will form the basis of an Exception Report 9
  10. 10. TASKHave issues within your project been fully documented?

×