Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

change management

1 reply [Last post]
Mo M
User offline. Last seen 31 weeks 6 days ago. Offline
Joined: 15 Feb 2007
Posts: 3

Would like your views on Change Management and specifically the change log.

is it good practice for risks that have materialised with time/cost/scope impact to be added to the change log and perhaps with an approved change form in addition to the risk register which may record the details of the actual risk occuring?

Replies

Patrick Weaver
User offline. Last seen 3 weeks 22 hours ago. Offline
Joined: 18 Jan 2001
Posts: 263
Groups: None

You seem to be confusing several documents:

Risks - things that may (or may not) happen in the future are recorded in a risk register for example: https://mosaicprojects.com.au/shop-risk-register.php

Problems that need resolving (often realized risks) are recorded in the issues log, see: https://mosaicprojects.com.au/WhitePapers/WP1089_Issues_Management.pdf  In the 'real world' many issues simply arise so this log is better kept as a separate document to the risk register.

The change log is a document used by the project change authorities to record requested changes in the scope of the project, or to controlled documents, and record the change request and what has how it has been actioned (rejected, approved, etc.). Managing risks and dealing with issues may, or may not require a formal change process. 

 Pat.