A project was sent for early customer testing and the customer reported that some of the features do not features do not meet the requirements. What should the project manager have done to avoid…

The correct answer is A. Engage customer earlier. Even though the project was sent for 'early' customer testing, features still failed to meet requirements - indicating insufficient customer involvement during development. The correct preventive action would have been to engage the customer even earlier in the process…

Agile Frameworks/Methodologies

Question

A project was sent for early customer testing and the customer reported that some of the features do not features do not meet the requirements. What should the project manager have done to avoid this scenario?

Options

AEngage customer earlier
BConduct quality audits
CValidate Scope
DValidate quality requirements

How the community answered

(53 responses)

A
81% (43)
B
6% (3)
C
4% (2)
D
9% (5)

Explanation

Even though the project was sent for 'early' customer testing, features still failed to meet requirements - indicating insufficient customer involvement during development. The correct preventive action would have been to engage the customer even earlier in the process, specifically during requirements definition and iteratively throughout development. Earlier and more continuous customer engagement ensures that requirements are correctly understood, prioritized, and validated before significant development effort is invested. This reflects the agile principle of continuous customer collaboration. Options B and C address quality assurance and scope validation but do not resolve the root cause, which is a gap in customer communication during development.

Topics

#Customer collaboration#Requirements management#Early feedback#Stakeholder engagement

Community Discussion

No community discussion yet for this question.

Full CAPM Practice