{"discuss":[{"ddate":"17-Apr-2013 03:38","dcontact":"MCdHp1","dtext":"Is there a way to quantify CoGQ and CoPQ, since these term means different things in different projects !","dtags":"","darch":"0"},{"ddate":"17-Apr-2013 07:38","dcontact":"MCeWiV","dtext":"<font face="Arial, Verdana" size="2">Quantification of CoGQ and CoPQ is subject to respective planning\/introspection.<\/font><div style="font-family: Arial, Verdana; font-size: 10pt; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;">For example let us take CoPQ,&nbsp;<\/div><div><font face="Arial, Verdana" size="2">1. Software , CoPQ = number of bugs customer reports (and failure to identify them before release and time taken to fix it. We arrive a cost for rework and equate them), or in Project release constraint perspective , project managers may knowingly release with Bugs citing the bugs are not&nbsp;show stoppers&nbsp;but minor (thereby quantifying&nbsp;the effort or work attention demanding to solve or ignore the bug existence).<\/font><\/div><div><font face="Arial, Verdana" size="2">2. Vehicle, CoPQ =&nbsp;<\/font><span style="font-family: Arial, Verdana; font-size: small;">Car Breakdown because of Tyre failure. CoPQ is because of wrong inspection of Tyre tread rubber, causing tyre wear or CoPQ is because of wrong methods of Tyre testing in varied weather condition causing tyre to burst. etc<\/span><\/div><div><span style="font-family: Arial, Verdana; font-size: small;"><br><\/span><\/div><div><font face="Arial, Verdana" size="2">So here we see CoPQ (Failure cost) being applied to Post release, Pre-release in Software and Inspection and Testing in Tyre case.<\/font><\/div><div><font face="Arial, Verdana" size="2"><br><\/font><\/div><div><font face="Arial, Verdana" size="2">Any clarification please feel to write down.<\/font><\/div><div><font face="Arial, Verdana" size="2">&nbsp;<\/font><\/div>","dtags":"CoQ","darch":"0"}]}