<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Quality Really IS Free</title>
	<atom:link href="http://www.stellman-greene.com/2006/03/29/quality-really-is-free/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stellman-greene.com/2006/03/29/quality-really-is-free/</link>
	<description>because for some weird reason, users want their software to work</description>
	<pubDate>Thu, 07 Aug 2008 23:06:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: manufacturing software</title>
		<link>http://www.stellman-greene.com/2006/03/29/quality-really-is-free/#comment-875</link>
		<dc:creator>manufacturing software</dc:creator>
		<pubDate>Fri, 01 Feb 2008 03:00:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.stellman-greene.com/blog/2006/03/29/quality-really-is-free/#comment-875</guid>
		<description>&lt;strong&gt;manufacturing software...&lt;/strong&gt;

We have very much promoted this type of business practice ourselves and am glad I came across your blog again. I have added you to our digg bookmarking account. Thanks!...</description>
		<content:encoded><![CDATA[<p><strong>manufacturing software&#8230;</strong></p>
<p>We have very much promoted this type of business practice ourselves and am glad I came across your blog again. I have added you to our digg bookmarking account. Thanks!&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SoftwareQualityEngineer</title>
		<link>http://www.stellman-greene.com/2006/03/29/quality-really-is-free/#comment-13</link>
		<dc:creator>SoftwareQualityEngineer</dc:creator>
		<pubDate>Sat, 07 Jul 2007 01:15:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.stellman-greene.com/blog/2006/03/29/quality-really-is-free/#comment-13</guid>
		<description>I feel this was very well written.  One thing I would like to not is the use of term “QA Team”.  I feel it has been so poorly defined, misused, and is not consistent in the software industry.  I think if Deeming, Juran, and Crosby could see where “quality” is being placed in many software projects they would turn over in their graves.  The “QA Team” does not constitute Software Testers.  Software Testers are Software Testers they are not Quality Assurance professionals.  It is my belief that a “QA Team” consists of Software Quality Engineers (SQE) that work hand in hand with Software Engineers throughout an entire software development life cycle through requirements, design, implementation, verification and validation, and software delivery to the customer.  If you want to obtain a Certified Software Quality Analyst (CSQA) or a Certified Software Quality Engineer (CSQE) http://www.softwarecertifications.com/qai_cqa.htm these have nothing to do with Software Testing.  Conversely if you want to obtain Certified Software Testing Engineer (CSTE) http://www.softwarecertifications.com/qai_cste.htm this has nothing to do with CSQA or CSQE.

Software Quality Engineers should be considered an integral part of the software team and are the eyes and ears of the software project.  So, how does SQEs work the software development life cycle?  SQE’s audit a software project’s compliance to it standards, plans, processes, and procedures.  Oh, you mean you should have standards, plans, processes, and procedures?  Maybe this is why software projects fail in the industry lack of having the necessary intelligence of establishing, managing, and backing standards, plans, processes, and procedures.  I have worked on many projects in various corporations that do not have standards, plans, processes and procedures.  So I bring up Crosby’s “conformance to requirements,” how can you have a quality product and verify “conformance to requirements,” if you do not have standards, plans, and procedures?  Are you going to levy the compliance to standards, plans, and procedures on the Software Testing Team?  The answer to that question is, Uh No.</description>
		<content:encoded><![CDATA[<p>I feel this was very well written.  One thing I would like to not is the use of term “QA Team”.  I feel it has been so poorly defined, misused, and is not consistent in the software industry.  I think if Deeming, Juran, and Crosby could see where “quality” is being placed in many software projects they would turn over in their graves.  The “QA Team” does not constitute Software Testers.  Software Testers are Software Testers they are not Quality Assurance professionals.  It is my belief that a “QA Team” consists of Software Quality Engineers (SQE) that work hand in hand with Software Engineers throughout an entire software development life cycle through requirements, design, implementation, verification and validation, and software delivery to the customer.  If you want to obtain a Certified Software Quality Analyst (CSQA) or a Certified Software Quality Engineer (CSQE) <a href="http://www.softwarecertifications.com/qai_cqa.htm" rel="nofollow">http://www.softwarecertifications.com/qai_cqa.htm</a> these have nothing to do with Software Testing.  Conversely if you want to obtain Certified Software Testing Engineer (CSTE) <a href="http://www.softwarecertifications.com/qai_cste.htm" rel="nofollow">http://www.softwarecertifications.com/qai_cste.htm</a> this has nothing to do with CSQA or CSQE.</p>
<p>Software Quality Engineers should be considered an integral part of the software team and are the eyes and ears of the software project.  So, how does SQEs work the software development life cycle?  SQE’s audit a software project’s compliance to it standards, plans, processes, and procedures.  Oh, you mean you should have standards, plans, processes, and procedures?  Maybe this is why software projects fail in the industry lack of having the necessary intelligence of establishing, managing, and backing standards, plans, processes, and procedures.  I have worked on many projects in various corporations that do not have standards, plans, processes and procedures.  So I bring up Crosby’s “conformance to requirements,” how can you have a quality product and verify “conformance to requirements,” if you do not have standards, plans, and procedures?  Are you going to levy the compliance to standards, plans, and procedures on the Software Testing Team?  The answer to that question is, Uh No.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
