What do you think about Validate scope and Control and as Validate scope the process of formalizing the final acceptance of a deleiverable why PMBOK brings control scope process after validate scope?
Essam LotfiProject Manager-MEP| TROJAN HoldingAbu Dhabi, United Arab Emirates
What do you think about Validate scope and Control and as Validate scope the process of formalizing the final acceptance of a deliverable why PMBOK brings control scope process after validate scope? or if we are talking about a general frame work should we consider the two processes could be running in parallel. Saving Changes...
We do not need to confuse ourselves with the sequence as there is no formal sequence in processes within a process group and it is loosely defined, Even within each process, the sequence in which items appear as input, tools and techniques, and outputs are in a weird sequence, not the way things should happen.
As far as validate scope and control scope are concerned, they have no formal relationship whatsoever. In Monitoring and Control we deal either with processes or deliverables. Deliverables are dealt with fist by Control Quality and then by Validate Scope, which is the deliverable inspection stream. Processes are checked for their conformance to their respective plans by the respective controls, like scope, schedule and cost.
Both Control Scope and Validate Scope, though belonging to a different stream are happening simultaneously and can bring about change requests to be processed by Integrated Change Control.
I would say, if there had to be a sequence between the two, Control Scope should come first. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The sequence of process execution is determined by you project life cycle. As you can read inside the PMBOK the numbers and sequence of process inside it is not a sign about you need to perform the process in that order. So, you can execute the process in the order you choose according to your project life cycle. Saving Changes...
