Posted: Sat Jun 09, 2007 2:37 am Post subject: Resubmit of failed changes
This question has sparked heated debate in our office. A change requester submits an RFC, let's call it Change A. Change A requires that several other changes have already been completed successfully, lets say Change B, Change C and Change D. Say Change A fails and is backed out and investigation finds the failure cause to be that Change D actually was not completed correctly. The person responsible for Change D makes the corrections and Change A can be attempted again. The question is: who is responsible for submitting a new RFC for Change A. The team making the original RFC says the person (or group) that was responsible for the failure should submit a new RFC for Change A, in my example that would be the Change D person. Others believe the original submitter should submit the new RFC for Change A regardless of what the reason for failure of earlier attempts is.
Joined: Jan 01, 2006 Posts: 500 Location: New Jersey
Posted: Sun Jun 10, 2007 12:53 am Post subject:
Why would you "close" the failed changes? Another option is to simple reject them, until corrective action is taken, and then promote them forward again, using the same RFCs. Doing it this way ensure that you have a complete audit trail of the work associated with a specific failed Change. If you create a new RFC, then you have the same related work thread spread over multiple RFCs. Many enterprises we deal with won't close failed Changes. They'll simply reject them backwards, until work is done to correct the issues, the re-promote them forward.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum