Task: Obtain User Acceptance Testing (UAT) Signoff

Signoff to acknowledge successful completion of UAT.

Purpose

To confirm that all UAT has been successfully completed and that the application or modification is ready for production deployment.

Relationships

Roles	Primary: Application Owner QA Lead	Additional: Project Manager QA Analyst UAT Tester	Assisting:
Inputs	Mandatory: Test Results or Dashboard	Optional: None	External: None
Outputs	Test Completion Certificate

Main Description

The QA Lead and Application Owner(s) is required to submit a completed Test Completion Certificate (TCC) to the Release Management Team, prior to any changes or new applications being deployed to production.

All Application Owners impacted by the role out of a new application, or by a modification to existing code must complete and submit a Test Completion Certificate with the guidance of the QA Lead. In the event there are compliance implications, a representative of the Bank’s Compliance Team, must also signoff on the TCC.

Application Owners and Compliance can provide the TCC with either a hard signature, or an electronic signature. An electronic signature is defined as an email, from the signor, with the completed TCC attached.

Steps

Obtain template of the TCC form

The TCC template is required for the sign off process.

Complete the TCC Form

Section 1 – Project Details - provide the following details
    o Project/Fix/Patch Name
    o EPMO Project #/CM Ticket
    o Planned Release date
    o Project Manager
    o Project Description
    o System(s) affected
    o Planned testing dates
    o Actual test activity completion date
Section 2 – Testing Activity Exit Status – Answer all questions
Section 3 – Comments and Signoff
    o Comments section is to allow the Technical Owner to enter any pertinent comments regarding testing activities.
    o TCC to be signed by the Technical Owner of record and sent to the QA Lead (see guidance section below for direction on acceptable forms of signature).

QA Lead Reviews the TCC Form

o To ensure all questions are satisfactorily answered.
o To ensure appropriate level of signoff(s) have been executed.
o Provide QA Signoff – this will be a hard signoff by the Release Manager.

Submit the TCC

The QA Lead will submit the final TCC to the appropriate governing body (PRB or TCCB).

Properties

Predecessor	Develop the QA Closure Report
Multiple Occurrences
Event Driven
Ongoing
Optional
Planned
Repeatable

Version and Release

Unified Life Cycle (ULC): 5.1, November 3, 2014
Phase Gates: 1.1, May 27, 2014
Process Engineering Process (PEP): 1.1, May 27, 2014