Wednesday, August 26, 2009

Being Agile with Kano Analysis

Kano analysis is a new product requirements tool that gives visualization to the relative merits, or value, of requirements. Agile is a project method that focus' on intimate customer involvement in the development of new user value.

The slideshow below gives some of the highpoints of the Kano tool in the context of the Agile method.

You will see that one quadrant of the Kano chart is the 'customer delight' quadrant. Here, often latent requirements emerge and become product 'ah-hah!'s. Ah-hah!s are the real discriminators. These are the ones that will fascinate users, heighten their interest in the project, and become the grist for early adopters.

It's around the ah-hah!s that you can build the project theme -- the real value proposition for the customer.

Are you networked on LinkedIn? If so, share this article with your network by clicking on the link.


  1. This is waaaay too jargon-y to mean anything to me.

    What does "agile" mean? How do you measure "product functionality" and why is it one-dimensional?

  2. Statistical innovation: 'Agile' refers to a body of knowledge about certain project management and technical practices, called "Agile" in the community, that call for developing products incrementally, letting the customer/user weigh in at every increment. This has the practical effect of making scope variable, and making the value proposition of the project dynamic as customers weigh benefits. See for more, and specifically the agile manifesto at You can also search this blog for 'agile' for

    Re 'one dimensional': that is a term given to Kano analysis by its Japanese author and refers to the graph of the "more is better" linear line.

    Re product functions: this is a matter of judgment, and subjective opinion, as to how product functions fit on the chart


Please add your value with a comment