Scribd Logo
Upload

Welcome to Scribd!

  • Risk Acceptance v1 0

    Uploaded by

    netnidhi
    14 views1 page
    This internal document is a risk acceptance form used when user acceptance testing (UAT) of a change fails but the change still needs to be implemented in a production system. The form collects information on the date UAT was performed, number of users tested, description of the UAT failure, justification for implementing the change despite the failure, whether the change requester accepts the risk, any remarks from the change requester, and whether the change assignee accepts ownership of the risk. It requires sign-off from the department head, system owner, and IT representative.

    Original Description:

    Original Title

    risk_acceptance_v1_0

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This internal document is a risk acceptance form used when user acceptance testing (UAT) of a change fails but the change still needs to be implemented in a production system. The form collects information on the date UAT was performed, number of users tested, description of the UAT failure, justification for implementing the change despite the failure, whether the change requester accepts the risk, any remarks from the change requester, and whether the change assignee accepts ownership of the risk. It requires sign-off from the department head, system owner, and IT representative.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    14 views1 page

    Risk Acceptance v1 0

    Uploaded by

    netnidhi
    This internal document is a risk acceptance form used when user acceptance testing (UAT) of a change fails but the change still needs to be implemented in a production system. The form collects information on the date UAT was performed, number of users tested, description of the UAT failure, justification for implementing the change despite the failure, whether the change requester accepts the risk, any remarks from the change requester, and whether the change assignee accepts ownership of the risk. It requires sign-off from the department head, system owner, and IT representative.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    of 1

    INTERNAL USE ONLY

    GROUP IT Issue Date: 24/01/11


    Issue / Rev No: 1.0

    RISK ACCEPTANCE FORM

    For unsuccessful UAT but when change has to For last minute changes
    be implemented in production systems

    UAT performed on
    (dd-mm-yyyy)

    Number of users tested

    Description of UAT failure


    (Please clearly indicate
    reasons for UAT failure)

    Justification for
    performing change in
    production systems
    despite UAT failure

    Change Requester
    acceptance (Yes/No)

    Change Requester
    remarks (if any)

    Change Assignee
    acceptance of risk
    ownership

    Department Head System Owner ITRE

    You might also like