Goals of the sprint

• Interfaces testing

• End-to-end testing (E2E) testing of the solution.

• Train the super-users = UAT testers

• Data quality test

Assumptions

• Testing is owned and managed by the customer

• Pricefx team is resolving the bugs and issues that could block the UAT progress

• No new requirements, no new development!

• The SIT & UAT runs on the QA partition unless agreed differently

Preparation to-dos

Create a separate sprint in Jira (“SIT & UAT”). It will gather the bugs detected during the testing

Load “production like” data in terms of the volume and structure. This is important to detect potential corner cases during the testing. The customer will not only test the functionalities of the system, but also the quality of their delivered data.

SIT (System Integration Testing)

The UAT can be merged with the SIT sub-sprint. Depends on agreement with the customer and/or partner.

UAT preparation

• Customer finalizes the test scenarios UAT, Pricefx performs the review.

• Training for the UAT testers. This is to make sure the tests go quick and smooth and there are no user errors logged as defects.

• Users, user groups, business roles set-up on partition.

UAT (User Acceptance Testing)

Duration depends on the number and complexity of the UAT scenarios. Plan with customer and compare the expected duration with the one in the SOW.

• Hint: don’t underestimate the capacity of Pricefx team, especially in the first week.

• Hint: the first days of the UAT are hectic. If possible, SA and CE should be on-site with the customer.

• Focus on the blocking bugs - prevent the UAT from getting stalled (Prio 1).

• Bug fixing and retesting is Prio 2. No new functionalities should be implemented!

Conclusion

• As the result of this sprint there should be GO/NO GO decision for Business go-live taken on the Steering Committee level.

• Optionally the go-live acceptance is signed off.

• The cutover plan is ready.

Artifacts:

1. Status report

2. Test script template

3. Cutover template

4. Acceptance protocol (Please upload this to the Project Status Page on Confluence.

Checklist for the UAT sprint:

1. Production ready data to be loaded in UAT environment. 
   Control both volume and quality of the data.
   Check both the system performance and data quality.

2. All test cases defined and uploaded in JIRA.

3. User acceptance tests go as planned.

4. Team has time to fix found defects.

5. Client is active, leads testing and communicates via JIRA.

6. Cutover planning to be finalized during UAT. Production instance is in place.

7. Go/nogo decision has been made and written acceptance of the solution received from client.