<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>ClearNet Security: Work on feature requests or try to code that really cool idea?</title>
    <link>http://blog.clearnetsec.com/articles/2007/02/27/work-on-feature-requests-or-try-to-code-that-really-cool-idea</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description></description>
    <item>
      <title>Work on feature requests or try to code that really cool idea?</title>
      <description>&lt;p&gt;
How do you balance a giant list of customer feature requests with your in-house splashes of innovative  ideas?  
&lt;/p&gt;
&lt;p&gt;
It seems really hard not to get buried coding incremental improvements while keeping your head above ground.  With your head buried, you&#8217;ll eventually lose sight of the vision and get blindsided by competitors.
&lt;/p&gt;
&lt;p&gt;
Several start-ups I&#8217;ve played at were driven almost entirely by customer requests.  I&#8217;m not debating the value of that.  But when it is used to control all the development cycles you begin to create a culture allergic to creativity and risk.
&lt;/p&gt;
&lt;p&gt;
Good team dynamics can help tremendously for encouraging members to be creative &#8211; I think the challenge is keeping it that way while championing a customer driven style of development.
&lt;/p&gt;


</description>
      <pubDate>Tue, 27 Feb 2007 20:32:00 -0700</pubDate>
      <guid isPermaLink="false">urn:uuid:f25c966a-457c-46c5-9635-9bdb95146460</guid>
      <author>tate@ClearNetSec.com (Tate Hansen)</author>
      <link>http://blog.clearnetsec.com/articles/2007/02/27/work-on-feature-requests-or-try-to-code-that-really-cool-idea</link>
      <category>ClearNet</category>
      <category>ClearNet Security</category>
      <category>Tate Hansen</category>
      <category>developing</category>
      <category>customer driven</category>
    </item>
  </channel>
</rss>
