<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://agileme.wiki/wiki/index.php?action=history&amp;feed=atom&amp;title=Kano_Analysis</id>
	<title>Kano Analysis - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://agileme.wiki/wiki/index.php?action=history&amp;feed=atom&amp;title=Kano_Analysis"/>
	<link rel="alternate" type="text/html" href="https://agileme.wiki/wiki/index.php?title=Kano_Analysis&amp;action=history"/>
	<updated>2026-05-12T15:41:34Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.38.6</generator>
	<entry>
		<id>https://agileme.wiki/wiki/index.php?title=Kano_Analysis&amp;diff=1335&amp;oldid=prev</id>
		<title>Mmusij: Created page with &quot;Category:Agile:ArticlesCategory:Agile  Kano analysis is a great way to define a good balance in your releases by categorising the features on a backlog from a customer...&quot;</title>
		<link rel="alternate" type="text/html" href="https://agileme.wiki/wiki/index.php?title=Kano_Analysis&amp;diff=1335&amp;oldid=prev"/>
		<updated>2021-05-25T03:53:01Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;&lt;a href=&quot;/wiki/Category:Agile:Articles&quot; title=&quot;Category:Agile:Articles&quot;&gt;Category:Agile:Articles&lt;/a&gt;&lt;a href=&quot;/wiki/Category:Agile&quot; title=&quot;Category:Agile&quot;&gt;Category:Agile&lt;/a&gt;  Kano analysis is a great way to define a good balance in your releases by categorising the features on a backlog from a customer...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;[[Category:Agile:Articles]][[Category:Agile]]&lt;br /&gt;
&lt;br /&gt;
Kano analysis is a great way to define a good balance in your releases by categorising the features on a backlog from a customer's perspective.&lt;br /&gt;
&lt;br /&gt;
==Catgorisation==&lt;br /&gt;
* '''Threshold''' - The minimum expectation. As a customer if I do not have this then I will not buy your product. In a smartphone example these might be the ability to make mobile telephone calls and send SMS messaging.&lt;br /&gt;
* '''Linear''' - Value added. As a customer the more of these features I get then the more utility and value I get from your product. In a smartphone example these might be email, internet, music capabilities that add more value to the device.&lt;br /&gt;
* '''Exciter''' - Unexpected value. As a customer I didn't expect to get these features, but now I am more inclined to buy your product over a competitor's. In a smartphone example think voice activated assistants, thumbprint recognition, voice recognition and facial recognition as unexpected exciters.&lt;br /&gt;
&lt;br /&gt;
==Balanced Releases==&lt;br /&gt;
To create a balanced release we might need to do all of the '''Threshold''' features, but maybe we can trade off a few '''Linear''' features to squeeze in a couple of '''Exciters'''. This would give us a nice balance of expected, added and unexpected value from each release.&lt;br /&gt;
&lt;br /&gt;
==Release Planning==&lt;br /&gt;
A good way to do this is to firstly categorise which features on a backlog are '''Threshold''', '''Linear''' or '''Exciter''' and then try to craft out a release with a little of everything to reach a nice balance. The difficulty is always how to get an exciter into a release when there is a lot of schedule pressure, but if it is possible to include at lease one '''Exciter''' then will this ease the schedule pressure going forwards?&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
* [https://en.wikipedia.org/wiki/Kano_model Kano Model]&lt;/div&gt;</summary>
		<author><name>Mmusij</name></author>
	</entry>
</feed>