A project team just completed a customer management solution. Following a gate review, stakeholders approved the solution for deployment. After deployment, however several reports claimed the new…

The correct answer is D. Lack of end-user acceptance testing. Post-deployment complaints about a difficult-to-navigate interface indicate that end users were not sufficiently involved in testing before go-live. End-user acceptance testing (UAT) is specifically designed to validate that real users can effectively interact with the system…

Project life cycle phases

Question

A project team just completed a customer management solution. Following a gate review, stakeholders approved the solution for deployment. After deployment, however several reports claimed the new interface was difficult to navigate. Which of the following is the MOST likely cause of this issue?

Options

AIncomplete scope of work
BImproper change management
CFailure to update the risk register
DLack of end-user acceptance testing

How the community answered

(46 responses)

A
22% (10)
B
7% (3)
C
11% (5)
D
61% (28)

Explanation

Post-deployment complaints about a difficult-to-navigate interface indicate that end users were not sufficiently involved in testing before go-live. End-user acceptance testing (UAT) is specifically designed to validate that real users can effectively interact with the system. The gate review and stakeholder approval (D) suggest the project followed change management (B) processes. An incomplete scope of work (A) would have caused missing features, not usability issues. Failing to update the risk register (C) is a documentation issue, not a cause of poor user experience.

Topics

#user acceptance testing#quality assurance#deployment#testing phases

Community Discussion

No community discussion yet for this question.

Full PK0-004 Practice