Difference between M&C and Verify Scope
Submitted by Shweta Ahuja on Tue, 09/18/2012 - 05:52
You are measuring the dimensions of a highly critical component in your project that was manufactured by one of your subcontractors. Failure of this component is a huge risk factor and would lead to major delays and possibly a failed project. In which process group does this activity belong ?
1. Project risk management
2. Monitoring and controlling
3. Verify Scope
4. Executing
Forums:
admin
Tue, 09/18/2012 - 06:02
Permalink
should be monitoring and
should be monitoring and control process group.
oorvashe
Tue, 09/18/2012 - 06:14
Permalink
It should be in Monitoring
It should be in Monitoring and controlling.
Ravi Moosad
Tue, 09/18/2012 - 06:29
Permalink
Its Quality Control
Inspecting the components manufactured by our subscontractor is a part of Quality Control and hence part of Monitoring and Controlling group. Verify Scope primarily focus on the formal acceptance of the final deliverable and this is usually done along with sponpor / customer representative.
Ravi Moosad, PMP
PMP DEN
Shweta Ahuja
Tue, 09/18/2012 - 06:32
Permalink
Thats what i thought.But this
Thats what i thought.
But this question made me think if the verify scope means formal acceptance of the deliverable then it has to be checked against the requirement before being accepted. Since validated deliverable is an input to verify scope, does it mean that formal checking of that deliverable against the requirement, whether it mets or not, is done in Perf Quality Control. Please confirm.
Thanks.
Ravi Moosad
Tue, 09/18/2012 - 07:20
Permalink
In verify scope, stakeholders
In verify scope, stakeholders accept (or reject) the deliverable validated by us. In this case, since the measurement is done by us, in my opinion, it is not verify scope but quality control which validates the deliverable and makes it ready for verify scope.
However, in subcontractors point of view, it will probably be verify scope process of his project .
Ravi Moosad, PMP
PMP DEN
Shweta Ahuja
Tue, 09/18/2012 - 06:45
Permalink
can you explain more how is
can you explain more how is inspection of components are part of QC.
Also verify scope is not just for final deliverable but intermediate deliverables as well.
Another question, there is no explicit deliverable coming out of the procurement KA. During the close procurement buyer just provides a formal letter of all work has been confirmed to be completed.
Is there any explicit deliverable (whatever the Proc SOW said was to be done by supplier) coming out of any Proc process ? If not then how is that deliverable integrated into the PM. Does that deliverable after handoff from seller become a part of just like any deliverables coming out of direct and manage work ?
Ravi Moosad
Tue, 09/18/2012 - 07:36
Permalink
In my opinion, Inputs to PQC
In my opinion, Inputs to PQC process include 'Deliverable'. Outputs include 'Validated Deliverable'. Among tools to the process you can find 'Inspection'. There is no mention of acceptance or stakeholder in this question, hence best assumption is that it is validation of a product which is part of QC.
You are right regarding interim deliverables. What I meant was 'Completed Deliverable' when I wrote 'Final Deliverable'.
Procurement activity is our internal process as far the customer is concerned. Hence, I think, there is no need for any specific deliverable for this activity. However, there will be deliverables from our vendor to us which is a different project / contract.
Ravi Moosad, PMP
PMP DEN