As for more complex projects 2 weeks of UAT is not enough, here is an example of how longer UAT can look like and what it should contain. Note that 6 weeks of UAT must be planned at the beginning of the project. Customer should be still responsible for UAT, but QA analyst can help if it is required. Note that customer must understand that they must be still prepared for UAT before those 6 weeks, when customer try to do preparation in those 6 weeks, they will not have enough time.
...
Proposed timelines and allocations:
Pre-UAT | Pre-UAT | UAT | UAT | ||
# of sprints | Training and prep | SIT | E2E testing | Bug fixing & testing | Total UAT weeks |
3 | 1 | 1 | 1 | 1 | 2 |
4 | 1 | 1 | 2 | 1 | 5 |
4 or 5 | 1 | 1 | 2 | 2 | 4 |
6 | 1 | 1 | 3 | 2 | 7 |
6 or 7 | 1 | 1 | 3 | 3 | 6 |
Role | Allocation | ||||
PM | same as FS allocation | ||||
SA | 50 % of FS allocation | ||||
CE | 50-75 % of FS allocation | ||||
IE | 25% of FS allocation | ||||
QA | 50-75 % of FS allocation | ||||
Internal description as Packages:
...
In case customer will not choose the size of UAT package, it will be selected based on number of Feature Sprints
Ppt slide deck which can be shared with the customer:
...
.
...
...
| Info |
|---|
You can learn about UAT on the project here. |
...