The article provides a detailed overview of the User Acceptance Testing (UAT) phase in a software development project, including prerequisites, tasks before UAT, tasks during UAT, and completion of the project. It also includes examples of project timelines and resource allocations for different project sizes.
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
For more complex projects, a 2-week UAT period may not suffice. Here's an example of what an extended UAT might entail and the necessary components. It's important to note that planning for a 6-week UAT should be done at the project's outset, and it serves as an illustration for larger projects. The fundamental expectations remain unchanged - the customer retains overall responsibility for UAT, although a QA analyst can provide assistance if needed.
...
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 | ||||
...