Thanks Rahul, helps a little. Regards MA

Hi Marc,

You are right. Actually there’s no “right order” for the Control Scope and Validate Scope processes. Control Scope can happen at any time, because project changes can happen at any time. Validate Scope is usually the last Scope Management process that you’ll do in a project. The trick is that sometimes you’ll find a scope problem while you’re verifying the scope, and you’ll need to do Control Scope and then go back and gather new requirements, rebuild the WBS, etc. So the Control Scope process can happen either before or after Validate Scope.

Hope this helps.

Hello,

Don't understand why PMI decided to first talk about 5.5 Validate Scope and then about 5.6 Control Quality in the PMBOK Guide. From a logical perspective, shouldn't these two processes switch their order in the guide? As Andy Crowe also mentioned in his prep book, Validate Scope comes either after Control Quality or it is performed at the same time. So, at 5.5 Validate Scope, the customer is included and accepts (hopefully) the created deliverables but from my point of view an internal 5.6 Control Quality should have taken place before we involve customer.

Can you explain?

Regards,
Marc