<?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: Prioritizing Software Requirements &#8211; Kano Take Two</title>
	<atom:link href="http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/</link>
	<description>Software product success.</description>
	<lastBuildDate>Sat, 19 May 2012 12:04:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Don’t Prioritize Features! &#124; devblogging.com</title>
		<link>http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/comment-page-1/#comment-805054</link>
		<dc:creator>Don’t Prioritize Features! &#124; devblogging.com</dc:creator>
		<pubDate>Thu, 21 Jul 2011 02:37:17 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/#comment-805054</guid>
		<description>[...] problem better,&#8221; or &#8220;solves more of the problem&#8221;) &#8211; which only applies to some problems &#8211; is interesting to some customers, in some market [...]</description>
		<content:encoded><![CDATA[<p>[...] problem better,&#8221; or &#8220;solves more of the problem&#8221;) &#8211; which only applies to some problems &#8211; is interesting to some customers, in some market [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ProdMgmt Talk</title>
		<link>http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/comment-page-1/#comment-770355</link>
		<dc:creator>ProdMgmt Talk</dc:creator>
		<pubDate>Wed, 16 Feb 2011 06:18:04 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/#comment-770355</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;RT @simonwitkiss: Reminded of Kano Analysis by @sehlhorst tweet http://bit.ly/eneH53 It&#039;s a different view on priorities when all is M i ...&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">RT @simonwitkiss: Reminded of Kano Analysis by @sehlhorst tweet <a href="http://bit.ly/eneH53" rel="nofollow">http://bit.ly/eneH53</a> It&#39;s a different view on priorities when all is M i &#8230;</span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Witkiss</title>
		<link>http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/comment-page-1/#comment-770356</link>
		<dc:creator>Simon Witkiss</dc:creator>
		<pubDate>Tue, 15 Feb 2011 21:26:11 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/#comment-770356</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;Reminded of Kano Analysis by @sehlhorst tweet http://bit.ly/eneH53 It&#039;s a different view on priorities when all is M in MoSCoW #prodmgmt #in&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Reminded of Kano Analysis by @sehlhorst tweet <a href="http://bit.ly/eneH53" rel="nofollow">http://bit.ly/eneH53</a> It&#39;s a different view on priorities when all is M in MoSCoW #prodmgmt #in</span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Little K&#8217;s Blog &#187; Blog Archive &#187; The featuritis Curve</title>
		<link>http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/comment-page-1/#comment-821</link>
		<dc:creator>Little K&#8217;s Blog &#187; Blog Archive &#187; The featuritis Curve</dc:creator>
		<pubDate>Sat, 15 Apr 2006 13:17:57 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/#comment-821</guid>
		<description>[...] When we use Kano analysis to prioritize features, we&#8217;re already halfway there (and then some). Recapping from that post: Kano provides three relevant classifications of requirements (the fourth category is redundant). All requirements can be placed in one of these categories. [...]</description>
		<content:encoded><![CDATA[<p>[...] When we use Kano analysis to prioritize features, we&rsquo;re already halfway there (and then some). Recapping from that post: Kano provides three relevant classifications of requirements (the fourth category is redundant). All requirements can be placed in one of these categories. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/comment-page-1/#comment-313</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Wed, 01 Mar 2006 21:00:47 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/#comment-313</guid>
		<description>Oops - sorry about the name confusion, Scott! :)</description>
		<content:encoded><![CDATA[<p>Oops &#8211; sorry about the name confusion, Scott! :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/comment-page-1/#comment-312</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Wed, 01 Mar 2006 15:54:36 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/#comment-312</guid>
		<description>I will definitely check it out - thanks for the link and the comment!  Welcome to Tyner Blain (btw - that&#039;s the company, I&#039;m Scott :)</description>
		<content:encoded><![CDATA[<p>I will definitely check it out &#8211; thanks for the link and the comment!  Welcome to Tyner Blain (btw &#8211; that&#8217;s the company, I&#8217;m Scott :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/comment-page-1/#comment-311</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Wed, 01 Mar 2006 04:56:57 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/#comment-311</guid>
		<description>Tyner,

I really enjoyed this post, thanks for the link to Moore&#039;s article too. Especially your point:
----
One of Mr. Moore’s points is that innovation isn’t the goal - product differentiation resulting from innovation is the goal. He’s absolutely right. An innovative way to minimize the window of an application isn’t likely to differentiate the product from it’s competitors.
----

Having been in the high-tech business for more than a decade, I&#039;m constantly surprised by the number of companies that mindlessly pursue innovations with no regard to meaningful product differentiation.

I posted a more detailed post on this point in my blog too - check it out when you get a chance:
http://michael.hightechproductmanagement.com/</description>
		<content:encoded><![CDATA[<p>Tyner,</p>
<p>I really enjoyed this post, thanks for the link to Moore&#8217;s article too. Especially your point:<br />
&#8212;-<br />
One of Mr. Moore’s points is that innovation isn’t the goal &#8211; product differentiation resulting from innovation is the goal. He’s absolutely right. An innovative way to minimize the window of an application isn’t likely to differentiate the product from it’s competitors.<br />
&#8212;-</p>
<p>Having been in the high-tech business for more than a decade, I&#8217;m constantly surprised by the number of companies that mindlessly pursue innovations with no regard to meaningful product differentiation.</p>
<p>I posted a more detailed post on this point in my blog too &#8211; check it out when you get a chance:<br />
<a href="http://michael.hightechproductmanagement.com/" rel="nofollow">http://michael.hightechproductmanagement.com/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

