Geeks With Blogs
Chris Breisch   .NET Data Practices
Search this Blog!

Most of my links are to good articles about coding practices.  But there’s more to software development than just coding.  Soctt Sehlhorst has written a great article on prioritizing software requirements using the four Kano categories:

  1. Surprise and delight. Capabilities that differentiate a product from it’s competition (e.g. the nav-wheel on an iPod).
  2. More is better. Dimensions along a continuum with a clear direction of increasing utility (e.g. battery life or song capacity).
  3. Must be. Functional barriers to entry - without these capabilities, customers will not use the product (e.g. UL approval).
  4. Better not be. Represents things that dissatisfy customers (e.g. inability to increase song capacity via upgrades).

Read the article to find out what he’s talking about.

Posted on Thursday, March 9, 2006 5:32 AM Architecture | Back to top

Comments on this post: Prioritizing Software Requirements

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Chris J. Breisch | Powered by: