Q - Scope Validation

[vikram_unde]

Hi Experts,

I am confused between two answers B or C. Can you help finding correct answer with clarification? (Source - Oliver)

What is true for the process of scope validation?

A Insufficient documentation is not a reason to reject deliverables, as long as in all other respects they are built according to specifications agreed upon.
B The project team members must achieve acceptance of the deliverables. This process is coordinated and documented by the project management team.
C It is the project management team’s responsibility to obtain stakeholder’s formal acceptance of the completed project scope and deliverables.
D Formal acceptance will finally reconcile all inconsistencies among deliverables and documents that where caused by bad change control and scope creep.

Regards,
Vikram Unde

[ankurjig]

I will choose C.

The reason will be the words 'formal acceptance of the deliverables from the stakeholders'.

It is not just acceptance of deliverables but formal acceptance or sign-off from the sponsor or customer that the project deliverables are as per the agreed requirements. This is similar to obtaining a User Acceptance Test (UAT) sign-off in software industry.

Ankur

[manishpn]

Agree with C

[vikram_unde]

I will choose C.

The reason will be the words 'formal acceptance of the deliverables from the stakeholders'.

It is not just acceptance of deliverables but formal acceptance or sign-off from the sponsor or customer that the project deliverables are as per the agreed requirements. This is similar to obtaining a User Acceptance Test (UAT) sign-off in software industry.

Ankur

Thanks Ankur!!

[bibhuti.s.das]

Fine, I agree with the logic that 'Formal Acceptance' implies Option C. But what's wrong in Option B. There it is only 'Acceptance', so B should be equally valid choice.
Please suggest!

[manishpn]

Ankutjig has aleady replied the logic why B is not the right option