Comments on: Prioritizing Software Requirements With Kano Analysis http://tynerblain.com/blog/2006/02/25/prioritizing-software-requirements-with-kano-analysis/ Software product success. Sun, 12 Feb 2012 19:10:25 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Scott Sehlhorst http://tynerblain.com/blog/2006/02/25/prioritizing-software-requirements-with-kano-analysis/comment-page-1/#comment-75952 Scott Sehlhorst Mon, 05 Mar 2007 15:09:35 +0000 http://tynerblain.com/blog/2006/02/25/prioritizing-software-requirements-with-kano-analysis/#comment-75952 Yes, several thoughts. :) I got a lot of feedback that this article, while providing information, didn't provide any guidance. So I wrote <a href="http://tynerblain.com/blog/2006/02/27/prioritizing-software-requirements-kano-take-two/" rel="nofollow">Kano Analysis: Take Two</a>. See if that helps any. Yes, several thoughts. :)

I got a lot of feedback that this article, while providing information, didn’t provide any guidance. So I wrote Kano Analysis: Take Two.

See if that helps any.

]]> By: Craig http://tynerblain.com/blog/2006/02/25/prioritizing-software-requirements-with-kano-analysis/comment-page-1/#comment-75802 Craig Mon, 05 Mar 2007 09:55:46 +0000 http://tynerblain.com/blog/2006/02/25/prioritizing-software-requirements-with-kano-analysis/#comment-75802 Kano helps you think about requirements and how they will be appreciated and perceived by the client but how do you prioritise a delighter o a more is better or a must have? Any thoughts? Kano helps you think about requirements and how they will be appreciated and perceived by the client but how do you prioritise a delighter o a more is better or a must have? Any thoughts?

]]>