<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: &#8220;Never promise a release date&#8221; vs. &#8220;Release early, release often&#8221;</title>
	<link>http://agylen.com/2005/05/03/never-promise-a-release-date-vs-release-early-release-often/</link>
	<description>Ugo Cei's Weblog</description>
	<pubDate>Tue, 06 Jan 2009 15:23:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Robert McIntosh</title>
		<link>http://agylen.com/2005/05/03/never-promise-a-release-date-vs-release-early-release-often/#comment-57</link>
		<dc:creator>Robert McIntosh</dc:creator>
		<pubDate>Wed, 04 May 2005 13:04:39 +0000</pubDate>
		<guid>http://agylen.com/2005/05/03/never-promise-a-release-date-vs-release-early-release-often/#comment-57</guid>
		<description>I don't see how "release early, release often" is promising a release date. Quite the opposite, if you release often, you don't have to promise a date, because your users/customers will know another release will be coming.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t see how &#8220;release early, release often&#8221; is promising a release date. Quite the opposite, if you release often, you don&#8217;t have to promise a date, because your users/customers will know another release will be coming.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Berin Loritsch</title>
		<link>http://agylen.com/2005/05/03/never-promise-a-release-date-vs-release-early-release-often/#comment-54</link>
		<dc:creator>Berin Loritsch</dc:creator>
		<pubDate>Tue, 03 May 2005 16:12:49 +0000</pubDate>
		<guid>http://agylen.com/2005/05/03/never-promise-a-release-date-vs-release-early-release-often/#comment-54</guid>
		<description>They can both be practiced without issues.  "Never promise a release date" is much more nerve racking if you don't release early and often.  My take is that you never promise a release date, you just release regularly.  You can recommend specific releases to your clients, but as long as you don't promise feature X will be here by such and such a date then you can work steadily toward it.</description>
		<content:encoded><![CDATA[<p>They can both be practiced without issues.  &#8220;Never promise a release date&#8221; is much more nerve racking if you don&#8217;t release early and often.  My take is that you never promise a release date, you just release regularly.  You can recommend specific releases to your clients, but as long as you don&#8217;t promise feature X will be here by such and such a date then you can work steadily toward it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
