Common UAT preparation aka Hardening (or "polishing") sprint
Goal of the sprint
Finalize the acceptance of all user stories
Upgrade to the latest Pricefx release
Load a full (production like) set of data.
The duration of this sprint depends on the project’s scope and complexity. The presumed duration for planning is 1 or 2 weeks, provided that typical prescriptive delivery takes four feature sprints.
It is supposed to run in parallel with the Performance sprint.
Finalize the acceptance of the user stories
No new configurations.
Only work on spill-over items, like bugs from the previous sprints.
Client finalizes all their unit testing, so UAT starts with a clean slate.
Upgrade week
Go-live to be on the latest stable release. Mind the N-1 policy. At this moment, the upgrade is easy and cheap.
Customer to perform the regression testing.
Partner/Pricefx to resolve the issues if any occur.
Full data load
The UAT should run on full, production-like set of data
SIT
Can be merged with the SIT sub-sprint. Depends on agreement with the customer and/or partner.