<?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: Agile UX Update: Sadness, Comfort, and Relief</title>
	<atom:link href="http://www.exfoo.com/2009/02/agile-ux-update-sadness-comfort-and-relief/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.exfoo.com/2009/02/agile-ux-update-sadness-comfort-and-relief/</link>
	<description>The Tim Richards Experience Experience</description>
	<lastBuildDate>Thu, 04 Mar 2010 11:35:07 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dutch</title>
		<link>http://www.exfoo.com/2009/02/agile-ux-update-sadness-comfort-and-relief/comment-page-1/#comment-82</link>
		<dc:creator>Dutch</dc:creator>
		<pubDate>Tue, 24 Feb 2009 01:27:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.exfoo.com/?p=188#comment-82</guid>
		<description>Yes! starting to knock off features from a a list of requirements will rarely make for a good product. 

Instead, identify treshold features (stuff customers expect), look at the problems/opportunity and identify exiters and delighters (the difference you will be providing) and start prioritizing these.

The remaining requirements of features should be categorized as OUT, also known as &quot;nice to have&quot;, and Linear (the more of these the more value) but these can come at a later stage.</description>
		<content:encoded><![CDATA[<p>Yes! starting to knock off features from a a list of requirements will rarely make for a good product. </p>
<p>Instead, identify treshold features (stuff customers expect), look at the problems/opportunity and identify exiters and delighters (the difference you will be providing) and start prioritizing these.</p>
<p>The remaining requirements of features should be categorized as OUT, also known as &#8220;nice to have&#8221;, and Linear (the more of these the more value) but these can come at a later stage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Krane</title>
		<link>http://www.exfoo.com/2009/02/agile-ux-update-sadness-comfort-and-relief/comment-page-1/#comment-53</link>
		<dc:creator>Joshua Krane</dc:creator>
		<pubDate>Tue, 03 Feb 2009 04:02:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.exfoo.com/?p=188#comment-53</guid>
		<description>This was really well thought out Tim, thanks!</description>
		<content:encoded><![CDATA[<p>This was really well thought out Tim, thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

