TOPIC: If customer validates scope do we always need to confirm final acceptance

If customer validates scope do we always need to confirm final acceptance of deliverable?

Hi Sharon,

validating scope implies the acceptance of completed deliverables, which is the output of this process. This becomes the input to the closing project/phase process, where the PM reviews project documentation, including confirmation of the formal acceptance of deliverable by the customer.

I understand it may be a little confusing, but I hope it helped a bit.

Gabriella

Concur. Since validating scope (formal acceptance) is not at closing, some answers say at closing the PM has to "confirm" final acceptance of deliverable. Is that always the case?

To be honest, I am always cautious regarding expressions like "always" or "never"
Anyway, in general I would agree about the need to "confirm" the final acceptance of deliverables in the closing project/phase project.

Gabriella

The "always" were my words, sorry. Thank you for confirming the need to "confirm" the final acceptance at closing.