<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Testing: What is a defect?</title>
	<atom:link href="http://www.markhneedham.com/blog/2008/12/18/testing-what-is-a-defect/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markhneedham.com/blog/2008/12/18/testing-what-is-a-defect/</link>
	<description>Thoughts on Software Development</description>
	<lastBuildDate>Sat, 11 Feb 2012 23:17:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jason Yip</title>
		<link>http://www.markhneedham.com/blog/2008/12/18/testing-what-is-a-defect/comment-page-1/#comment-2175</link>
		<dc:creator>Jason Yip</dc:creator>
		<pubDate>Sat, 20 Dec 2008 23:22:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=752#comment-2175</guid>
		<description>It&#039;s worth looking at Lean Product Development and the Toyota Product Development System to understand how to think about this better.  What we&#039;re really thinking about is efficiency of detection.  Some &quot;defects&quot; are really things we are learning about how the technology works.  If we are having to re-learn, that&#039;s a defect.

One way to think about this is that testing to a specification is waste (although perhaps necessary waste) while testing to understand boundaries is quite valuable.</description>
		<content:encoded><![CDATA[<p>It&#8217;s worth looking at Lean Product Development and the Toyota Product Development System to understand how to think about this better.  What we&#8217;re really thinking about is efficiency of detection.  Some &#8220;defects&#8221; are really things we are learning about how the technology works.  If we are having to re-learn, that&#8217;s a defect.</p>
<p>One way to think about this is that testing to a specification is waste (although perhaps necessary waste) while testing to understand boundaries is quite valuable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank Carver&#8217;s Punch Barrel / More thoughts on defects in an agile process</title>
		<link>http://www.markhneedham.com/blog/2008/12/18/testing-what-is-a-defect/comment-page-1/#comment-2129</link>
		<dc:creator>Frank Carver&#8217;s Punch Barrel / More thoughts on defects in an agile process</dc:creator>
		<pubDate>Fri, 19 Dec 2008 08:31:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=752#comment-2129</guid>
		<description>[...] Testing: What is a defect? at Mark Needham [...]</description>
		<content:encoded><![CDATA[<p>[...] Testing: What is a defect? at Mark Needham [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

