<?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>Kommentare zu: Building the Right Product with Hypothesis-Driven Development</title>
	<atom:link href="http://blog.hendrikbeck.com/2013/01/16/building-the-right-product-with-hypothesis-driven-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hendrikbeck.com/2013/01/16/building-the-right-product-with-hypothesis-driven-development/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=building-the-right-product-with-hypothesis-driven-development</link>
	<description>Tech Startup Craftsmanship</description>
	<lastBuildDate>Sun, 03 Apr 2016 21:59:00 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.8.1</generator>
	<item>
		<title>Von: Rita Nguyen</title>
		<link>http://blog.hendrikbeck.com/2013/01/16/building-the-right-product-with-hypothesis-driven-development/#comment-34</link>
		<dc:creator><![CDATA[Rita Nguyen]]></dc:creator>
		<pubDate>Thu, 17 Jan 2013 07:05:16 +0000</pubDate>
		<guid isPermaLink="false">https://hendrikbeck.wordpress.com/?p=372#comment-34</guid>
		<description><![CDATA[Cool post.  I just realized that you had responded to my comment from the previous post :)  

To clarify a bit, I didn&#039;t mean the right product for the market, I meant if the product is built to scope.  I like this approach above but I don&#039;t think that you have to use a hypothesis-driven product approach in order to do continuous releases.  Done right, your product counterparts are working with dev to still write stories, etc, etc.  My only point being that you need to make sure that automation testing isn&#039;t the only testing that is being relied upon.  That kind of testing is great to make sure builds are stable/bug free for continuous deployment as they do not catch if something is supposed to be green or blue.]]></description>
		<content:encoded><![CDATA[<p>Cool post.  I just realized that you had responded to my comment from the previous post <img src="http://blog.hendrikbeck.com/wp-includes/images/smilies/icon_smile.gif" alt=":)" class="wp-smiley" />   </p>
<p>To clarify a bit, I didn&#8217;t mean the right product for the market, I meant if the product is built to scope.  I like this approach above but I don&#8217;t think that you have to use a hypothesis-driven product approach in order to do continuous releases.  Done right, your product counterparts are working with dev to still write stories, etc, etc.  My only point being that you need to make sure that automation testing isn&#8217;t the only testing that is being relied upon.  That kind of testing is great to make sure builds are stable/bug free for continuous deployment as they do not catch if something is supposed to be green or blue.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
