<?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 Impact of Change and Use Cases</title>
	<atom:link href="http://tynerblain.com/blog/2006/07/24/the-impact-of-change-and-use-cases/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2006/07/24/the-impact-of-change-and-use-cases/</link>
	<description>Software product success.</description>
	<lastBuildDate>Sun, 12 Feb 2012 19:10:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/07/24/the-impact-of-change-and-use-cases/comment-page-1/#comment-54499</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Wed, 26 Jul 2006 04:07:40 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/07/24/the-impact-of-change-and-use-cases/#comment-54499</guid>
		<description>Thanks!</description>
		<content:encoded><![CDATA[<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deepak</title>
		<link>http://tynerblain.com/blog/2006/07/24/the-impact-of-change-and-use-cases/comment-page-1/#comment-54497</link>
		<dc:creator>Deepak</dc:creator>
		<pubDate>Tue, 25 Jul 2006 19:16:33 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/07/24/the-impact-of-change-and-use-cases/#comment-54497</guid>
		<description>I think you hit the nail on the head.  What I was listing is important for the intial release, but for subsequent incremental releases, it is very important to manage customer expectations, and deliver usability value in a somewhat predictable timeframe (without getting tied down by the constraints of date driven releases)</description>
		<content:encoded><![CDATA[<p>I think you hit the nail on the head.  What I was listing is important for the intial release, but for subsequent incremental releases, it is very important to manage customer expectations, and deliver usability value in a somewhat predictable timeframe (without getting tied down by the constraints of date driven releases)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/07/24/the-impact-of-change-and-use-cases/comment-page-1/#comment-54494</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Tue, 25 Jul 2006 19:01:25 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/07/24/the-impact-of-change-and-use-cases/#comment-54494</guid>
		<description>Deepak, thanks for the comment!

I agree that the business cares about delivery in &quot;valuable chunks&quot;, usually at the market requirement level.  Incremental delivery processes tend to take this one step smaller, and deliver at the smallest &quot;consumable&quot; chunk size.  While &lt;i&gt;interim&lt;/i&gt; chunks might not provide incremental business value, they will create an environment for feedback from the users.  And some incremental releases will generate business value.

As you point out, it is important to manage expectations when communicating with the customer about this type of delivery.  Some releases generate value (in use) and all incremental releases generate value (in feedback).</description>
		<content:encoded><![CDATA[<p>Deepak, thanks for the comment!</p>
<p>I agree that the business cares about delivery in &#8220;valuable chunks&#8221;, usually at the market requirement level.  Incremental delivery processes tend to take this one step smaller, and deliver at the smallest &#8220;consumable&#8221; chunk size.  While <i>interim</i> chunks might not provide incremental business value, they will create an environment for feedback from the users.  And some incremental releases will generate business value.</p>
<p>As you point out, it is important to manage expectations when communicating with the customer about this type of delivery.  Some releases generate value (in use) and all incremental releases generate value (in feedback).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deepak</title>
		<link>http://tynerblain.com/blog/2006/07/24/the-impact-of-change-and-use-cases/comment-page-1/#comment-54493</link>
		<dc:creator>Deepak</dc:creator>
		<pubDate>Tue, 25 Jul 2006 18:55:14 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/07/24/the-impact-of-change-and-use-cases/#comment-54493</guid>
		<description>There is definitely one danger to the iterative process (or perhaps a flag that needs to be removed early in the process).  Product managers should be careful what is the minimal set of functionality that will make their customers see value in the product.  Providing a roadmap that shows where the functionality is going helps, but if a certain threshold of user needs is not met, in my experience, customers get very annoyed.</description>
		<content:encoded><![CDATA[<p>There is definitely one danger to the iterative process (or perhaps a flag that needs to be removed early in the process).  Product managers should be careful what is the minimal set of functionality that will make their customers see value in the product.  Providing a roadmap that shows where the functionality is going helps, but if a certain threshold of user needs is not met, in my experience, customers get very annoyed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

