<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: The Illusion Of One Dimensional Quality</title>
	<link>http://blog.qualityaspect.com/2006/04/28/the-illusion-of-one-dimensional-quality/</link>
	<description>Lidor Wyssocky's Blog on Optimizing Software Development</description>
	<pubDate>Wed, 20 Aug 2008 12:56:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on The Illusion Of One Dimensional Quality by: Lidor Wyssocky</title>
		<link>http://blog.qualityaspect.com/2006/04/28/the-illusion-of-one-dimensional-quality/#comment-194</link>
		<pubDate>Sat, 29 Apr 2006 16:45:46 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/04/28/the-illusion-of-one-dimensional-quality/#comment-194</guid>
					<description>&lt;p&gt;
Hi Scott, 

&lt;/p&gt;&lt;p&gt;Thanks for responding to the article review. 

&lt;/p&gt;&lt;p&gt;I agree with your approach regarding the communication with customers. But I think there is still a need to emphasize the improtance of internal quality. 
&lt;/p&gt;&lt;p&gt;By that I am not referring solely to internal metrics (such as the one you mentioned in your comment). Internal quality deals with entirely different aspects of the product: its maintainability and extensibility as reflected in the quality of its design and code. 
&lt;/p&gt;&lt;p&gt;This is not just another metric, nor is it the quality of the process. It is part of the quality of the product, but not its functional quality. Maybe the customer does not care about these qualities (although I believe he does, implicitly). But other stakeholders should have these attributes at the top of their list...

&lt;/p&gt;&lt;p&gt;Lidor&lt;/p&gt;</description>
		<content:encoded><![CDATA[	<p>
Hi Scott, </p>
	<p>Thanks for responding to the article review. </p>
	<p>I agree with your approach regarding the communication with customers. But I think there is still a need to emphasize the improtance of internal quality.
</p>
	<p>By that I am not referring solely to internal metrics (such as the one you mentioned in your comment). Internal quality deals with entirely different aspects of the product: its maintainability and extensibility as reflected in the quality of its design and code.
</p>
	<p>This is not just another metric, nor is it the quality of the process. It is part of the quality of the product, but not its functional quality. Maybe the customer does not care about these qualities (although I believe he does, implicitly). But other stakeholders should have these attributes at the top of their list&#8230;</p>
	<p>Lidor</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on The Illusion Of One Dimensional Quality by: Scott Sehlhorst</title>
		<link>http://blog.qualityaspect.com/2006/04/28/the-illusion-of-one-dimensional-quality/#comment-193</link>
		<pubDate>Sat, 29 Apr 2006 16:17:04 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/04/28/the-illusion-of-one-dimensional-quality/#comment-193</guid>
					<description>This is definitely the most eloquent critique of anything I've written.  Thanks very much.

I used customer and stakeholder interchangeably in that post - probably not a good idea.  What I was trying to capture was the idea of &quot;everyone not on the team, who cares about the output of the team.&quot;  I think of all of those people as customers, not just the people who give us money.

I completely agree that maintaining internal quality is critical to success.  My point was that while it is important to the people on the team, the only thing that is important to people not on the team is the result of that high internal quality.

The analogy of a plant manager for a manufacturing site holds pretty well, I think.  That plant manager tells his customers about the defect rate in shipped products - that's how quality is shared.  Inside the building, that plant manager reviews control charts, six sigma reports, sampling data and status reports from every element of the manufacturing system.  By monitoring those controls, he can make sure that he delivers a low shipped-product-defect-rate.  The plant manager isn't going to tell the customer that the spring-angle on the contact arms is running at +/- 1.8 sigma within tolerance bounds.  

Granted, some customers may want to audit the quality processes - but this isn't the common-course for communication, and should be treated as the exception to the rule that it is.

Thanks again for your great feedback, and thanks for reading.  I hope you'll stay with us, and continue to point out where we can do better!

Scott</description>
		<content:encoded><![CDATA[	<p>This is definitely the most eloquent critique of anything I&#8217;ve written.  Thanks very much.</p>
	<p>I used customer and stakeholder interchangeably in that post - probably not a good idea.  What I was trying to capture was the idea of &#8220;everyone not on the team, who cares about the output of the team.&#8221;  I think of all of those people as customers, not just the people who give us money.</p>
	<p>I completely agree that maintaining internal quality is critical to success.  My point was that while it is important to the people on the team, the only thing that is important to people not on the team is the result of that high internal quality.</p>
	<p>The analogy of a plant manager for a manufacturing site holds pretty well, I think.  That plant manager tells his customers about the defect rate in shipped products - that&#8217;s how quality is shared.  Inside the building, that plant manager reviews control charts, six sigma reports, sampling data and status reports from every element of the manufacturing system.  By monitoring those controls, he can make sure that he delivers a low shipped-product-defect-rate.  The plant manager isn&#8217;t going to tell the customer that the spring-angle on the contact arms is running at +/- 1.8 sigma within tolerance bounds.  </p>
	<p>Granted, some customers may want to audit the quality processes - but this isn&#8217;t the common-course for communication, and should be treated as the exception to the rule that it is.</p>
	<p>Thanks again for your great feedback, and thanks for reading.  I hope you&#8217;ll stay with us, and continue to point out where we can do better!</p>
	<p>Scott
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
