forum.izenbridge.com

Thanks Manish - the state " a low grade of quality may not be a problem" threw me off. and I agree and will keep in mind that your point about project deliverable being of low quality.
Rose

[quote=ralapatt post_id=42158 time=1605569331 user_id=15983]
Please help with this question from iZenbridge and there is an issues the answer options. the word "a low grade of quality may not be a problem" is incorrect. [b][color=#0080FF]I Agree[/color][/b]
it should be "a low grade of product may not be a problem"
[color=#0080FF][b]Again Agree[/b][/color]
Which is why I chose answer D - Because both quality and grade be low it is per project requirement
[color=#0080FF][b]We need to understand, that no project will ask for lower quality product/Deliverables, hence I will not go with option D
[/b][/color]
[i][b]please write email to support@izenbridge.com to rectify the option
[/b][/i]
Question 26 
1.00/0.00
Moses is a project manager and working on quality of his project. He is always confused between grade and quality. He is never able to make a bottom line which one can be compromised on the cost of other. Which is the below can help Moses understanding the true fundamental of grade and quality?
•  
A quality level that fails to meet quality requirements is always a problem, a low grade of quality may not be a problem.
•  
A grade level that fails to meet quality requirements is always a problem, a low quality may not be a problem.
•  
Both quality and grade are mandatory and should not be low at any cost
•  
Both quality and grade can be low as per project requirement
-
Solution
It is general quality management concept.
Quality and grade are not the same concepts. Quality as a delivered performance or result is “the degree to which a set of inherent characteristics fulfill requirements”. Grade as a design intent is a category assigned to deliverables having the same functional use but different technical characteristics. The project manager and the project management team are responsible for managing the trade-offs associated with delivering the required levels of both quality and grade. While a quality level that fails to meet quality requirements is always a problem, a low grade of quality may not be a problem PMBOK 274

Thank you Rose
[/quote]

Please help with this question from iZenbridge and there is an issues the answer options. the word "a low grade of quality may not be a problem" is incorrect. it should be "a low grade of product may not be a problem" Which is why I chose answer D - Because both quality and grade be low it is per project requirement

Question 26 
1.00/0.00
Moses is a project manager and working on quality of his project. He is always confused between grade and quality. He is never able to make a bottom line which one can be compromised on the cost of other. Which is the below can help Moses understanding the true fundamental of grade and quality?
•  
A quality level that fails to meet quality requirements is always a problem, a low grade of quality may not be a problem.
•  
A grade level that fails to meet quality requirements is always a problem, a low quality may not be a problem.
•  
Both quality and grade are mandatory and should not be low at any cost
•  
Both quality and grade can be low as per project requirement
-
Solution
It is general quality management concept.
Quality and grade are not the same concepts. Quality as a delivered performance or result is “the degree to which a set of inherent characteristics fulfill requirements”. Grade as a design intent is a category assigned to deliverables having the same functional use but different technical characteristics. The project manager and the project management team are responsible for managing the trade-offs associated with delivering the required levels of both quality and grade. While a quality level that fails to meet quality requirements is always a problem, a low grade of quality may not be a problem PMBOK 274

Thank you Rose