The Forgotten Side of Quality

Jeff Patton explains how Kano model is applied while adding features to a product:

The Kano Method separates product features into general categories. The three big ones are “must haves,” like: brakes on a car (we need those); “one-dimensional” items like gas mileage on a car (higher mileage is better); and attractive quality or “delighters” (leather seats in my German car are a delighter). The idea is that your product should have all the must haves, maximize the one-dimensionals, and toss in some delighters.

A common problem with most softwares and products, in general:

In software development, more features is often considered better. Since we’re consumed with the quantity of features, we often forget the quality of the software as a whole unit.

How to fix this problem:

  1. In a small group, brainstorm the major features of your product.
  2. Independently for each feature write your “grade” for the quality of the feature. Answer the following questions: Do you like the feature?; Do you like using it?; and Is it a valuable part of the product? Let your answers help you grade the feature with an A, B, C, or D, or fail it with an F.
  3. When done, discuss your grades with those in your group. Agree on a grade that best represents the group’s opinion of the quality of that feature.

Read the article

No Comments

Add your comment

Comments are closed.