<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Building a Reputation: Knowing When to Experiment and When to Deliver</title>
	<link>http://www.retrospector.com/2006/06/09/building-a-reputation-knowing-when-to-experiment-and-when-to-deliver/</link>
	<description>A hindsight perspective on the everlasting trail of improvement.</description>
	<pubDate>Fri, 05 Dec 2008 08:31:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Wrapping up the Project: Completing Deliverables &#183; The Retrospector</title>
		<link>http://www.retrospector.com/2006/06/09/building-a-reputation-knowing-when-to-experiment-and-when-to-deliver/#comment-1916</link>
		<pubDate>Mon, 17 Jul 2006 06:21:00 +0000</pubDate>
		<guid>http://www.retrospector.com/2006/06/09/building-a-reputation-knowing-when-to-experiment-and-when-to-deliver/#comment-1916</guid>
					<description>[...] During the lifetime of the project from concept to delivery, you absolutely must delay new features such that they be brought back into the picture after the first delivery unless the stakeholders are willing to deal with a huge time delay. Check out my post on knowing when to experiment and when to deliver for more related points on delivery focus.  Want or Requirement? [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] During the lifetime of the project from concept to delivery, you absolutely must delay new features such that they be brought back into the picture after the first delivery unless the stakeholders are willing to deal with a huge time delay. Check out my post on knowing when to experiment and when to deliver for more related points on delivery focus.  Want or Requirement? [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
