<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="2.0" xml:base="http://www.kai-mai.com">
<channel>
 <title>Kai Mai&#039;s Blog - Take Back the Web - Nodes for feature</title>
 <link>http://www.kai-mai.com/tags/feature</link>
 <description>Nodes containing the tag feature</description>
 <language>en</language>
<item>
 <title>Too Many Features?  How to Prioritize and Trade off Product Features?</title>
 <link>http://www.kai-mai.com/node/162</link>
 <description>&lt;p&gt;
When you develop a product, if you run into the problem of having too few features, you should pause building it cause you haven&#039;t thought through.
&lt;/p&gt;
&lt;p&gt;
But like most people, you dream of new killer features day and night and end up with too many of them.  Unless you are working on a brand new products, you&#039;d have bugs/enhancements to deal with.
&lt;/p&gt;
&lt;p&gt;
Here&#039;s my ordered criteria for feature/bug fixing/enhancements prioritization and trade-off:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt; Business/Sales/Marketing
&lt;ol&gt;
&lt;li&gt; Does it solve customer&#039;s problems?  Does it address customer&#039;s pain points? Stop dreaming of cool features that don&#039;t solve actual problems.
&lt;/ol&gt;
&lt;/ul&gt;
&lt;p class=&quot;awTags_TagLinks&quot;&gt;Tags: &lt;a href=&quot;tags/329&quot;&gt;feature&lt;/a&gt; &lt;a href=&quot;tags/330&quot;&gt;proritization&lt;/a&gt; &lt;a href=&quot;tags/331&quot;&gt;product_management&lt;/a&gt; &lt;/p&gt;</description>
 <category domain="http://www.technorati.com/tag">feature</category>
 <category domain="http://www.technorati.com/tag">proritization</category>
 <category domain="http://www.technorati.com/tag">product_management</category>
 <pubDate>Fri, 30 Jan 2009 13:29:47 -0800</pubDate>
</item>
</channel>
</rss>
