<?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: The Balance Between Prevention and Inspection</title>
	<atom:link href="http://www.mikkeman.nl/blog/2010/03/the-balance-between-prevention-and-inspection/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mikkeman.nl/blog/2010/03/the-balance-between-prevention-and-inspection/</link>
	<description>better is worse than good enough - thoughts on lean and agile project management</description>
	<lastBuildDate>Wed, 08 Sep 2010 09:15:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Douwe Pieter van den Bos</title>
		<link>http://www.mikkeman.nl/blog/2010/03/the-balance-between-prevention-and-inspection/comment-page-1/#comment-117</link>
		<dc:creator>Douwe Pieter van den Bos</dc:creator>
		<pubDate>Wed, 19 May 2010 08:48:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikkeman.nl/blog/?p=174#comment-117</guid>
		<description>Hi there Martin,

Of course, you&#039;re right. Prevention is always better than inspection and rework. But it also states an impasse (if this is also an english term, but you&#039;re Dutch, so you probably understand what I mean). Too much prevention will slow down to a point where prevention will undermine progress within the project. In my point of view, there&#039;s only one possibility: more prototyping and short lines to the end users. When it comes to testing, the only real important part is the acceptance test by the end users, for two reasons: first the users will test if the software checks with their demands, second, the users will have the sheer feeling that they matter.

What&#039;s your thought on this? And have you ever encoutered a project where testing didn&#039;t add value to the product?

Regards and thanks for the post!

Douwe Pieter</description>
		<content:encoded><![CDATA[<p>Hi there Martin,</p>
<p>Of course, you&#8217;re right. Prevention is always better than inspection and rework. But it also states an impasse (if this is also an english term, but you&#8217;re Dutch, so you probably understand what I mean). Too much prevention will slow down to a point where prevention will undermine progress within the project. In my point of view, there&#8217;s only one possibility: more prototyping and short lines to the end users. When it comes to testing, the only real important part is the acceptance test by the end users, for two reasons: first the users will test if the software checks with their demands, second, the users will have the sheer feeling that they matter.</p>
<p>What&#8217;s your thought on this? And have you ever encoutered a project where testing didn&#8217;t add value to the product?</p>
<p>Regards and thanks for the post!</p>
<p>Douwe Pieter</p>
]]></content:encoded>
	</item>
</channel>
</rss>

