Compliance to User Acceptance 2781
goodchild last edited by
In our organization, the normal process for data or small configuration changes allows user/requester acceptance AFTER the change is performed. Our rfc system is also designed to include this workflow beofre close-completion of the request.
However, many of the requesters do not bother to user approve in the rfc system, probably because the request has alredy been served and its a waste of time. Now the rfc system is filled with incomplete requests.
Any ideas on how to deal with this?
Thanks very much.
kymike last edited by
Require user acceptance prior to migrating the changes to production. Once migrated, you lose all leverage in getting a sign-off.