The Kano Model: Developing for Value and Delight

Even though we have been developing software on the mainframe platform for decades we still have ways to learn and improve. We continually face the problem of meeting user needs with the resources we have on hand. This forces us to be careful about what we choose to do—we must look at whether we are focusing on the right things. While there are basic expectations that must be met, are we providing things that excite and delight? That is, the things that make users feel connected and generate passion. Users that feel a connection with your applications can obtain greater value from them.

How to provide things that excite while still delivering on basic needs is difficult to manage, but there are tools to help. For one the Kano model created by Japanese educator, lecturer, writer, and consultant in the field of quality management, Dr. Noriaki Kano. He sought to resolve these issues with a prioritization framework. The framework focuses on the three patterns of customer expectations versus the investments organizations make to delight their customers and do what it takes to positively impact customer satisfaction.

Creating Happy Customers With DevOps in 8 Hours or Less [Report]

We recently ran a survey against the software testing community to understand the adoption of modern development practices and its impact on testing.

One of the things we wanted to take away from this survey was being able to identify effective DevOps practices from harmful ones. We based the success criteria on team satisfaction and customer happiness.