<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.ninjitsuweb.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Project Planning</title>
 <link>http://www.ninjitsuweb.com/articles/planning</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en</language>
<item>
 <title>Web Projects that Succeed</title>
 <link>http://www.ninjitsuweb.com/agile</link>
 <description>&lt;div style=&quot;float:right;width: 33%; line-height:1em; font-size:2em; color:#777; margin:.5em 0 0 .5em;&quot;&gt;When you plan for &lt;em&gt;features&lt;/em&gt; instead of planning for &lt;em&gt;change&lt;/em&gt;, you are planning to &lt;em&gt;fail&lt;/em&gt;.&lt;/div&gt;
&lt;p&gt;No one has ever come to us with a project they started with some other developer that failed in the &lt;a href=&#039;/planning&#039;&gt;Planning Stage&lt;/a&gt;. During planning, everyone is excited, and developers can say &quot;yes&quot; to every request, because no real work is being done. It&#039;s all just ideas floating in the collective imagination of everyone involved. &lt;/p&gt;
&lt;p&gt;Unfortunately, there&#039;s no such thing as a &quot;collective imagination.&quot; Inevitably, everyone imagines something slightly different from anyone else. Decisions made in a Planning Stage are always based on limited information and unrevealed assumptions.&lt;/p&gt;
&lt;p&gt;This is what causes project to fail in the Execution Stage. Once work begins, the dreamers disengage, and naively expect that all their hopes will magically come true without any intervention on their part. Only when the developers come back with a disappointing delivery many weeks or months later does the client realize that the people involved were never speaking the same language. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.ninjitsuweb.com/agile&quot; target=&quot;_blank&quot;&gt;&lt;strong&gt;&amp;nbsp;read&amp;nbsp;more&amp;nbsp;&amp;raquo;&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
</description>
 <comments>http://www.ninjitsuweb.com/agile#comments</comments>
 <category domain="http://www.ninjitsuweb.com/articles/planning">Project Planning</category>
 <pubDate>Mon, 13 Apr 2009 11:55:02 -0700</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">56 at http://www.ninjitsuweb.com</guid>
</item>
<item>
 <title>Tips for planning your Web Project</title>
 <link>http://www.ninjitsuweb.com/planning</link>
 <description>&lt;p&gt;We hear from a lot of people who know that they need to get their communications, processes, and data online, but they don&#039;t know where to go from there. Here&#039;s some advice on how to plan for your project, and how to find a Web Developer who can meet your needs. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.ninjitsuweb.com/planning&quot; target=&quot;_blank&quot;&gt;&lt;strong&gt;&amp;nbsp;read&amp;nbsp;more&amp;nbsp;&amp;raquo;&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
</description>
 <comments>http://www.ninjitsuweb.com/planning#comments</comments>
 <category domain="http://www.ninjitsuweb.com/articles/planning">Project Planning</category>
 <pubDate>Mon, 26 Jan 2009 12:30:02 -0800</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">45 at http://www.ninjitsuweb.com</guid>
</item>
<item>
 <title>Building a Better Blog</title>
 <link>http://www.ninjitsuweb.com/articles/blogging-tools</link>
 <description>&lt;div style=&quot;float:right;&quot;&gt;
  &lt;img src=&quot;/files/Crystal_Clear_app_kedit.png&quot;?&gt;
&lt;/div&gt;
&lt;p&gt;For anyone with a &#039;simple&#039; &#039;blog project seems like there are two questions that always need to be answered:&lt;/p&gt;
&lt;p&gt;1.) Which software to use?&lt;/p&gt;
&lt;p&gt;2.) How to do this as inexpensively as possible?&lt;/p&gt;
&lt;p&gt;As to question #1 (software), I fully admit a bias toward Drupal, but I will try to give a somewhat objective overview of your choices. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.ninjitsuweb.com/articles/blogging-tools&quot; target=&quot;_blank&quot;&gt;&lt;strong&gt;&amp;nbsp;read&amp;nbsp;more&amp;nbsp;&amp;raquo;&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
</description>
 <comments>http://www.ninjitsuweb.com/articles/blogging-tools#comments</comments>
 <category domain="http://www.ninjitsuweb.com/articles/planning">Project Planning</category>
 <category domain="http://www.ninjitsuweb.com/articles/drupal">Why Drupal?</category>
 <pubDate>Tue, 09 Jun 2009 20:55:45 -0700</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">64 at http://www.ninjitsuweb.com</guid>
</item>
<item>
 <title>On Hiring Drupal Developers</title>
 <link>http://www.ninjitsuweb.com/node/49</link>
 <description>&lt;p&gt;Every technology that becomes widely popular as quickly as Drupal has will certainly attract individuals looking for a quick buck, without concern for real skills and experience. &lt;/p&gt;
&lt;p&gt;Drupal&#039;s incredible flexibility means that most problems can be solved in more than one way; but some of those ways are not &quot;The Drupal Way&quot; and can result in more time and expense down the road, when you want to change or expand your site. We are frequently contacted by organizations who had hired a previous developer who couldn&#039;t deliver what was needed, or who delivered a mess of code that had to be untangled before new work could begin. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.ninjitsuweb.com/node/49&quot; target=&quot;_blank&quot;&gt;&lt;strong&gt;&amp;nbsp;read&amp;nbsp;more&amp;nbsp;&amp;raquo;&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
</description>
 <comments>http://www.ninjitsuweb.com/node/49#comments</comments>
 <category domain="http://www.ninjitsuweb.com/articles/planning">Project Planning</category>
 <pubDate>Tue, 13 Jan 2009 07:32:08 -0800</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">49 at http://www.ninjitsuweb.com</guid>
</item>
</channel>
</rss>
