Difference between quality control & scope verification 1

[soheilpakazad]

Dear Friends,

Would you please help me to understand the difference between scope verification and quality control .

Are they different in meaning and function or philosephy ?

Thank you very much for your help,

Warmest regards,

Soheil Pak Azad

 

[IRstuff]

Huh? One sounds like something to do with contract management, which is only loosely related to quality control.

http://www.mypmps.net/en/mypmps/knowledgeareas/scope/scope-verification.html

TTFN

FAQ731-376

 

[zeusfaber]

Where I work, these are two different approaches to the problem of trying to get adequate quality in a bought-in product or service.

Scope-verification is the modern and elightened approach, which involves getting somebody else to check that the scope of the potential supplier's ISO 900n quality certification includes all the things you want them to do for you.

Quality Control is an old-fashioned approach favoured by the hard-bitten and involves getting a good look at the suppliers' output/product to see if it's any good.

A.

 

[pennpiper]

If you are smart you will do both.

 

[soheilpakazad]

Thank you very much for your comments,but in a text I read,the difference between scope verification and quality control were as follows but still I did not get the meaning:

scope verification: concerned with the acceptance of the deliverable

quality control: concerned with meeting the quality requirements specified for the deliverable .

But the above definition is still vague for me,


Soheil Pak Azad

 

[PeterStock]

As I read zeusfaber's post, scope verification involves confirming that the vendor is capable of producing the desired item. Quality control is confirming that they did if fact do so. The first should be done before selecting them as a vendor, the 2nd should be done for first articles at least.

Peter Stockhausen
Senior Design Analyst (Checker)
Infotech Aerospace Services

http://www.infotechpr.net

 

[FreddyNurk]

Your perspective may change depending on whether you're looking at something internally (say, project management of a new power station) or looking at purchasing a widget.

For my employer, where we are the people that provide services to construct a new power station, the following may be used as a loose translation:

Scope Verification: What we will do as the service provider

Quality Control: Are we doing what we said we would

Scope verification is useful for determining who is doing what, who isn't doing what, and if multiple people are involved, where the boundaries are.

 

[davsy]

My experience pretty much follows the PMBOK guide which states:

"Scope Verification differs from Quality Control in that Scope Verification is primarily concerned with acceptance of the deliverables, while Quality Control is primarily concerned with the correctness of the deliverables and meeting the quality requirements specified for the deliverables. Control Quality is generally performed before verify scope, but these two processes can be performed in parallel"

Source: Section 5.4 of the 4th Edition- A guide to the Project Management Body of Knowledge.

Formally signing off a deliverable acceptance is typically Scope Verification. Issuing a snagging list of things that need to be put right, repaired or completed before sign off can occur is typically Quality Control.

Quality Control quite often is an ongoing process, in some companies it starts during the time a proposeal is assembled and continues all the way through a project right to the end and even follows through into post project service support. Scope Verification only happens at certain points and or sometimes only once at the very end when the product or service is accepted as complete.

As pennpiper says above, if you are smart you will do both.