UAT sprint

Goal for the sprint:

the solution has been tested by customer to assure it can handle required tasks, according to user stories and system requirements.

Actions:

1. Provide Testing script template to customer ( if requested)

2. Review and confirm with the customer the project test script

3. Transfer the test cases into the JIRA and create Test board

4. Make sure the QA environment is ready for testing (data loaded, all developments has been transferred and tested by Pfx)

5. Schedule the calls for frequent testing feedback with customer

6. Document all bugs and changes into the JIRA

7. Access the impact of bugs/changes on budget and project timeline

8. If Testing has been successfully accomplished, request the written confirmation of the acceptance from the customer

9. The cutover planning should start

Checklist for UAT sprint:

1. Production ready data needs to be loaded in UAT environment - both from volume and quality point of view. This to ensure we test both the system performance and data quality.

2. The test cases are defined and uploaded in JIRA (even if there are only 5 of those).

3. The user acceptance tests are going as planned.

4. Your team has time to fix the defects.

5. The customer is following the testing procedures and leaves the feedback in JIRA.

6. The Cutover planning has started and has been discussed with customer.

7. Written acceptance of the solution has been sent by customer.