In the week 3 lecture, Dr. Simon taught us about design change request, which is used when someone find mistake that need to change or has suggestion that need to add, and this is part of monitoring and controlling stage. All documents DID, DDP, DSD, Verification/Validation Protocols, Risk Analysis, Risk Management Plan can be changed by this request. Also, Dr. Simon said the design change request should be written based on the latest version of the desired document. In my previous job, I received a design change request that wasn't created based on the latest version of the document, and I wrote this document at the beginning of the project, so I didn't remember the previous changes. As a result of this that wasted my and my team time. Is there a way to avoid the situation like this?
If you received the design change request that was based on the current version, it would be best to have rejected the request and ask the person submitting the request to refer to the latest version or revision of the document. It may be a good note for your team to start to check before any document release that each change request is based upon latest versions of the DHF as line items and specifications can change between each revision (and does quite frequently). Earlier is better than later for document changes to not waste time on having to redo the work your team has already put in.
Since this type of situation does occur from time to time where revisions do not match up after the lion's share of the work is complete, it would also be good to ensure that each revision of the DHF has a redlined version uploaded each time it is revised. If you are able to have the previous version with redlines and the new version for comparison, it may not be that hard to update your documents unless it is a major change (in that case, a noncompliance may occur which is another can of worms in change request). Overall, a procedure for an initial check as well as document upload rules can aid in change request revision misalignment.
