User Acceptance Testing involves significant participation from our customers (OD).

We at SR would have to ensure that we work with the BUs (OD) right from the requirement definition stage to effectively participate and manage the user acceptance testing process. User Acceptance Testing Services validate end-to-end business process, system transactions and user access, confirms the system or application is functionally fit for use and behaves as expected. Also, identifies areas where user needs are not included in the system or the needs are incorrectly specified or interpreted in the system.

Currently the process followed at AD and OD does not involve significant preparation for UAT (User Acceptance Testing). Going forward the SR PM team has to work in tandem with BU to ensure that certain key deliverables are in place well ahead of the UAT testing phase . Once the requirements have been finalized and an estimate is received by the Development and Quality Assurance teams at AD .The UAT testing team(OD) would have to prepare test cases and ensure that all the necessary data requirements have been communicated to the AD PM team . The AD PM team would then work with the UAT Support team and request for data well in advance of the UAT testing schedule . Proposed Changes Planning: The UAT strategy is outlined during the planning step. This would be achieved by maintaining a UAT test Plan mentioning Designing test cases: Test cases are designed to cover all the functional scenarios of the software in real-world usage. They are designed in a simple language and manner to make the test process easier for the testers. Selection of testing team: The testing team is comprised of real world end-users. Executing test cases and documenting: The testing team executes the designed test cases. Sometimes it also executes some relevant random tests. All bugs are logged in a testing document with relevant comments. Bug fixing: Responding to the bugs found by the testing team, the software development team makes final adjustments to the code to make the software bug-free. Sign-off: When all bugs have been fixed, the testing team indicates acceptance of the software application. This shows that the application meets user requirements and is ready to be rolled out .

Roles and Responsibilities:

Business Analyst: BA ensures requirements are signed off by the BU BA/ AD UAT works with the BU to understand Test Scenarios ( Real World + Normal Scenarios ) BA /AD UAT would understand data requirements and request the same from the UAT Support team. BA/AD UAT would work with the BU to understand who would be conducting UAT (The BU requestor will assign a team of users to conduct UAT. BA ensure UAT environment is ready for the testing to take place .

UAT Analyst : Ensures UAT team has a UAT test a UAT test plan in place before UAT testing happens. Ensures UAT test cases for the user story is documented by OD .Reviews the test cases Coordinate with the UAT Support at AD to ensure data requirements are ready well ahead of the UAT phase.

UAT Support:

Ensure UAT environment readiness and also provides data required for User to conduct UAT .

UAT team (OD): UAT test planning Preparation of Test cases Communicate data requirements to the PM team. Execution of Test cases during the UAT phase Report and document defects found during UAT Provide Sign off to the BA handling the specific requirement

Key Deliverables UAT Test Plan UAT test cases UAT test log : A log of all the test cases executed and the actual results

Entry Criteria : User Stories documented by the BA UAT test scenarios Acceptance criteria UAT environment Completion of QA testing with no critical defects or show stoppers

Exit Criteria : Test Summary Decision to go live or not UAT sign off - Customer buy-in, indicating BU finds the product delivered to their satisfaction