Comments on: Prioritizing Software Requirements – Kano Take Two http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/ Software product success. Thu, 18 Mar 2010 20:39:50 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Little K’s Blog » Blog Archive » The featuritis Curve http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/comment-page-1/#comment-821 Little K’s Blog » Blog Archive » The featuritis Curve Sat, 15 Apr 2006 13:17:57 +0000 http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/#comment-821 [...] When we use Kano analysis to prioritize features, we’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. [...] [...] When we use Kano analysis to prioritize features, we’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. [...]

]]> By: Michael http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/comment-page-1/#comment-313 Michael Wed, 01 Mar 2006 21:00:47 +0000 http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/#comment-313 Oops - sorry about the name confusion, Scott! :) Oops – sorry about the name confusion, Scott! :)

]]> By: Scott Sehlhorst http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/comment-page-1/#comment-312 Scott Sehlhorst Wed, 01 Mar 2006 15:54:36 +0000 http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/#comment-312 I will definitely check it out - thanks for the link and the comment! Welcome to Tyner Blain (btw - that's the company, I'm Scott :) I will definitely check it out – thanks for the link and the comment! Welcome to Tyner Blain (btw – that’s the company, I’m Scott :)

]]> By: Michael http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/comment-page-1/#comment-311 Michael Wed, 01 Mar 2006 04:56:57 +0000 http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/#comment-311 Tyner, I really enjoyed this post, thanks for the link to Moore'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'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/ Tyner,

I really enjoyed this post, thanks for the link to Moore’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’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/

]]>