7.6k views
2 votes
Which of the following is not a guideline for project acceptance?

a. Get customer sign-off on Acceptance Test Procedures before testing begins

b. Do not stray from Acceptance Test Procedures

c. Strive for objective, verifiable evidence of completion

d. Encourage development of new requirements by the users

e. Limit changes to address only essential defects to be fixed (the goal is to stabilize the system)

User Xochitl
by
8.4k points

1 Answer

1 vote

Final answer:

The guideline not recommended for project acceptance is 'Encourage development of new requirements by the users' as it can destabilize the project and lead to scope creep.

Step-by-step explanation:

The guideline for project acceptance that is not recommended is d. Encourage development of new requirements by the users. When managing project acceptance, it is essential to adhere to established Acceptance Test Procedures and limit changes during the testing phase to essential defect fixes only. The goal is to stabilize the system, not to introduce new variables by adding requirements, which can lead to scope creep and destabilization of the project.

Acceptance testing should provide objective, verifiable evidence of completion, and any changes to the project should be critically assessed to ensure that they address only essential defects. It is crucial also to have customer sign-off on Acceptance Test Procedures before testing begins to ensure that all parties agree on the criteria for acceptance.

User Nduplessis
by
8.5k points