George LewisProgram/Project Manager| DXC Technology CompanyHeredia, Costa Rica
What other questions would you ask when Studying Project Quality Management?
1. Difference between attribute sampling and variable sampling
2. Difference between normal Audit and Procurement Audit and Quality Audit
3. Difference between quality control, perform quality assurance, plan quality management and scope verification
4. Difference between scope baseline, schedule baseline, cost baseline
5. Difference between sensitivity analysis, variance analysis
6. Difference between special (random) causes and special causes
7. Difference between trend analysis and variance analysis
8. Difference between Quality and Grade
Quality Management should be based on the client's requirement. The requirements should dictate your questions. If you are doing right things then you will have use cases or process documented.
Now for each process/use case, you should decide the quality matrix with your client/stakeholders.
Use case1: response time, integrity of response, authenticity, risk, challenge-ability etc.
You need to work with quality matrix and ask questions around it. Saving Changes...
Praveen MalikIndependent Consultant| Independent ConsultantNew Delhi, India
Jun 30, 2016 1:36 PM
Replying to Sungjoon Park
...
Dear Praveen,
Thank you for introduction of your blog article.
Based on page 248 in PMBOK, Control Quality process can identify the poor process and recommend or take corrective actions, so it might not be recommendable to distinguish one from another by applying to specific target like processes or deliverables. Both can be inspected in the Control Quality Processes and deliverables are not necessarily completed when Control Quality Process should begin.
In my opinion, in case of no further information provided, it is hardly possible to know which of two is implementing.
Anyway, your article on this issue is great. Thanks a lot.
Regards,
Park
Hi Sungjoon, Pg 248 say "identifying the
causes of poor process" and not identify the poor process itself.
...
1 reply by Sungjoon Park
Jul 05, 2016 3:14 AM
Sungjoon Park
...
Dear Praveen,
Thank you for your reply. You may have different opinions which I appreciate..
The article is more of interpretation of the PMBOK Guide than my opinion. As per my reading, PMBOK Guide does not say (on pg. 248 or elsewhere) "Control Quality can identify poor processes".
On the other hand, in many companies the term QA is used for "testing products" and QC is used for "analyzing processes". It just means that they are following their own (different) standards.
BR.
Saving Changes...
Praveen MalikIndependent Consultant| Independent ConsultantNew Delhi, India
Jul 05, 2016 3:14 AM
Replying to Sungjoon Park
...
Dear Praveen,
Thank you for your reply. You may have different opinions which I appreciate..
The article is more of interpretation of the PMBOK Guide than my opinion. As per my reading, PMBOK Guide does not say (on pg. 248 or elsewhere) "Control Quality can identify poor processes".
On the other hand, in many companies the term QA is used for "testing products" and QC is used for "analyzing processes". It just means that they are following their own (different) standards.
BR.
...
1 reply by Sungjoon Park
Jul 05, 2016 1:13 PM
Sungjoon Park
...
Dear Praveen,
Thanks for your reply. I agree with you.
However, as per my understanding of the PMBOK, if it measures against standards or plans and produces Quality Control Measurements as an output, it should be considered as Control Quality whether it inspects the processes or products. Assurance means "prevention over inspection" using the "Quality Control Measurements during executing stage. Quality Assurance may be carried out during even earlier stage to ensure that standards or policies setup in the project are effective prior to Quality Control.
Quality Assurance may be executed in any stage of project life cycle before closing the project while Quality Control may be used when processes are executed, and when deliverables are produced or completed mainly in executing and closing stages.
Stages mentioned above should not be considered as Process Groups.
Regards,
Park
Saving Changes...
William M Hayden JrAdjunct Assistant Professor| University at Buffalo, School of Management, Operations Management & StrategyBuffalo, Ny, United States
At the project's inception, what and how does the project manager translate the client's "Expectations" into "Requirements," and then confirm with the client that the derived "Requirements" once met will meet that client's "Expectations." Once completed, now, for the first time, may the PM have the technical functions translate the "Requirements" into approriate levels of technical "Specifications."
Quailty is meeting requirements.
Cheers,
Bill Saving Changes...
The article is more of interpretation of the PMBOK Guide than my opinion. As per my reading, PMBOK Guide does not say (on pg. 248 or elsewhere) "Control Quality can identify poor processes".
On the other hand, in many companies the term QA is used for "testing products" and QC is used for "analyzing processes". It just means that they are following their own (different) standards.
BR.
Dear Praveen,
Thanks for your reply. I agree with you.
However, as per my understanding of the PMBOK, if it measures against standards or plans and produces Quality Control Measurements as an output, it should be considered as Control Quality whether it inspects the processes or products. Assurance means "prevention over inspection" using the "Quality Control Measurements during executing stage. Quality Assurance may be carried out during even earlier stage to ensure that standards or policies setup in the project are effective prior to Quality Control.
Quality Assurance may be executed in any stage of project life cycle before closing the project while Quality Control may be used when processes are executed, and when deliverables are produced or completed mainly in executing and closing stages.
Stages mentioned above should not be considered as Process Groups.
