<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Why do SharePoint Projects Fail? &#8211; Part 8</title>
	<atom:link href="http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/</link>
	<description>After much frustration, it seems DEFAULT is the way to go...</description>
	<lastBuildDate>Mon, 15 Mar 2010 19:32:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Adam Wright</title>
		<link>http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/comment-page-1/#comment-25075</link>
		<dc:creator>Adam Wright</dc:creator>
		<pubDate>Thu, 04 Mar 2010 04:08:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/#comment-25075</guid>
		<description>Paul, all I can say is wow. Great series!!!  I was actually searching for some entertaining reading on &quot;SharePoint Horror Stories&quot; and ended up finding your series.  This series is full of points of wisdom and excellent links to other relevant and as intriguing articles.  I can definitely say this series will be one I reference frequently in the future when dealing with wicked problems.  I will probably also point some managers and stakeholders to pieces of this series in order to try to help educate them about how essential the roles they play are in projects.  Please let me know if you do or have put this out as a white paper.  I believe that would be priceless. Once again fantastic work.</description>
		<content:encoded><![CDATA[<p>Paul, all I can say is wow. Great series!!!  I was actually searching for some entertaining reading on &#8220;SharePoint Horror Stories&#8221; and ended up finding your series.  This series is full of points of wisdom and excellent links to other relevant and as intriguing articles.  I can definitely say this series will be one I reference frequently in the future when dealing with wicked problems.  I will probably also point some managers and stakeholders to pieces of this series in order to try to help educate them about how essential the roles they play are in projects.  Please let me know if you do or have put this out as a white paper.  I believe that would be priceless. Once again fantastic work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KirstennU28</title>
		<link>http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/comment-page-1/#comment-20377</link>
		<dc:creator>KirstennU28</dc:creator>
		<pubDate>Fri, 08 Jan 2010 20:14:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/#comment-20377</guid>
		<description>Do you present the &lt;a href=&quot;http://www.4writers.net&quot; rel=&quot;nofollow&quot;&gt;freelance writing &lt;/a&gt;? Your information connecting to this topic seems to be smashing.</description>
		<content:encoded><![CDATA[<p>Do you present the <a href="http://www.4writers.net" rel="nofollow">freelance writing </a>? Your information connecting to this topic seems to be smashing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The One Best Practice to Rule Them All: Part 3 &#124; End User SharePoint</title>
		<link>http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/comment-page-1/#comment-7008</link>
		<dc:creator>The One Best Practice to Rule Them All: Part 3 &#124; End User SharePoint</dc:creator>
		<pubDate>Mon, 16 Mar 2009 14:46:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/#comment-7008</guid>
		<description>[...] has been around since&#8230; forever. I wrote in more detail about the perils of waterfall in the project fail series in the section &quot;how we really solve [...]</description>
		<content:encoded><![CDATA[<p>[...] has been around since&hellip; forever. I wrote in more detail about the perils of waterfall in the project fail series in the section &quot;how we really solve [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray</title>
		<link>http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/comment-page-1/#comment-6832</link>
		<dc:creator>Ray</dc:creator>
		<pubDate>Wed, 11 Mar 2009 21:47:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/#comment-6832</guid>
		<description>Paul - I ran across this series and read the entire posting, 1 to 8, this afternoon.  Very insightful and thought provoking.  I am in the early planning phases of a SharePoint implementation and will put the info in this series to good use.
Thank you for taking the time to share your thoughts and experience.</description>
		<content:encoded><![CDATA[<p>Paul &#8211; I ran across this series and read the entire posting, 1 to 8, this afternoon.  Very insightful and thought provoking.  I am in the early planning phases of a SharePoint implementation and will put the info in this series to good use.<br />
Thank you for taking the time to share your thoughts and experience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/comment-page-1/#comment-6373</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sun, 01 Mar 2009 01:34:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/#comment-6373</guid>
		<description>Kailash, I am a big fan of your blog and your writings, so your feedback is immensely gratifying.</description>
		<content:encoded><![CDATA[<p>Kailash, I am a big fan of your blog and your writings, so your feedback is immensely gratifying.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kailash Awati</title>
		<link>http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/comment-page-1/#comment-6372</link>
		<dc:creator>Kailash Awati</dc:creator>
		<pubDate>Sun, 01 Mar 2009 01:27:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/#comment-6372</guid>
		<description>Paul,

I printed out the entire series to read over the weekend. Just finished reading through, and all I can say is, &quot;I wish I&#039;d written it myself.&quot;  Thanks for a brilliant analysis of why projects fail.

As I&#039;m sure you&#039;re aware, the difficulty of achieving a shared understanding in software projects was also highlighted by Brooks in his classic article, &lt;a href=&quot;http://www.virtualschool.edu/mon/SoftwareEngineering/BrooksNoSilverBullet.html&quot; rel=&quot;nofollow&quot;&gt;No Silver Bullet&lt;/a&gt;. A quote from the paper is particularly apposite:

&lt;i&gt;&quot;...I believe the hard part of building software to be the specification, design, and testing of this conceptual construct, not the labor of representing it and testing the fidelity of the representation. We still make syntax errors, to be sure; but they are fuzz compared with the conceptual errors in most systems.

If this is true, building software will always be hard. There is inherently no silver bullet...&quot;&lt;/i&gt;

Brooks mentions four inherent, irreducible properties of software systems: complexity, conformity, changeability and invisibility. A while ago I wrote a piece entitled, &lt;a href=&quot;http://eight2late.wordpress.com/2008/05/04/on-the-intrinsic-complexity-of-it-projects/&quot; rel=&quot;nofollow&quot;&gt;On the intrinsic complexity of IT projects&lt;/a&gt;, wherein I discuss the connections between Brooks&#039; analysis of the software systems and technical project management.  

Thanks again for your entertaining and edifying analysis of why projects fail -  links to the series will be forwarded to friends and colleagues shortly.

Regards,

Kailash.</description>
		<content:encoded><![CDATA[<p>Paul,</p>
<p>I printed out the entire series to read over the weekend. Just finished reading through, and all I can say is, &#8220;I wish I&#8217;d written it myself.&#8221;  Thanks for a brilliant analysis of why projects fail.</p>
<p>As I&#8217;m sure you&#8217;re aware, the difficulty of achieving a shared understanding in software projects was also highlighted by Brooks in his classic article, <a href="http://www.virtualschool.edu/mon/SoftwareEngineering/BrooksNoSilverBullet.html" rel="nofollow">No Silver Bullet</a>. A quote from the paper is particularly apposite:</p>
<p><i>&#8220;&#8230;I believe the hard part of building software to be the specification, design, and testing of this conceptual construct, not the labor of representing it and testing the fidelity of the representation. We still make syntax errors, to be sure; but they are fuzz compared with the conceptual errors in most systems.</p>
<p>If this is true, building software will always be hard. There is inherently no silver bullet&#8230;&#8221;</i></p>
<p>Brooks mentions four inherent, irreducible properties of software systems: complexity, conformity, changeability and invisibility. A while ago I wrote a piece entitled, <a href="http://eight2late.wordpress.com/2008/05/04/on-the-intrinsic-complexity-of-it-projects/" rel="nofollow">On the intrinsic complexity of IT projects</a>, wherein I discuss the connections between Brooks&#8217; analysis of the software systems and technical project management.  </p>
<p>Thanks again for your entertaining and edifying analysis of why projects fail &#8211;  links to the series will be forwarded to friends and colleagues shortly.</p>
<p>Regards,</p>
<p>Kailash.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CleverWorkarounds &#187; The one best practice to rule them all - Part 1</title>
		<link>http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/comment-page-1/#comment-5708</link>
		<dc:creator>CleverWorkarounds &#187; The one best practice to rule them all - Part 1</dc:creator>
		<pubDate>Wed, 11 Feb 2009 21:25:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/#comment-5708</guid>
		<description>[...] and in fact, most *encourage* you to take the bits that make logical sense for you. As I wrote in Part 8 of the &quot;SharePoint Project Failure&#8230;&quot; series, I found it ironic that implementation [...]</description>
		<content:encoded><![CDATA[<p>[...] and in fact, most *encourage* you to take the bits that make logical sense for you. As I wrote in Part 8 of the &quot;SharePoint Project Failure&#8230;&quot; series, I found it ironic that implementation [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart</title>
		<link>http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/comment-page-1/#comment-5288</link>
		<dc:creator>Stuart</dc:creator>
		<pubDate>Fri, 30 Jan 2009 07:41:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/#comment-5288</guid>
		<description>I am in the unenviable position of trying to foster a more mature approach to support for our organisation.  We already use Sharepoint in a very limited capacity as an intranet portal, and some thought was going towards turning it into an all singing all dancing toy.
After reading all this, I am content to use it as a very simple document repository to start with.  It can do ONE thing well for now, and when I know how it performs for that, I will integrate the others.  Stably.</description>
		<content:encoded><![CDATA[<p>I am in the unenviable position of trying to foster a more mature approach to support for our organisation.  We already use Sharepoint in a very limited capacity as an intranet portal, and some thought was going towards turning it into an all singing all dancing toy.<br />
After reading all this, I am content to use it as a very simple document repository to start with.  It can do ONE thing well for now, and when I know how it performs for that, I will integrate the others.  Stably.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron Turnbull</title>
		<link>http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/comment-page-1/#comment-2407</link>
		<dc:creator>Ron Turnbull</dc:creator>
		<pubDate>Thu, 11 Sep 2008 12:25:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/#comment-2407</guid>
		<description>Spot on.  I read the entire set of articles from start to finish. Interesting, enlightening and entertaining.  Can&#039;t wait to recommend this to our SharePoint team!</description>
		<content:encoded><![CDATA[<p>Spot on.  I read the entire set of articles from start to finish. Interesting, enlightening and entertaining.  Can&#8217;t wait to recommend this to our SharePoint team!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/comment-page-1/#comment-687</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 06 Jun 2008 02:57:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/2008/06/03/why-do-sharepoint-projects-fail-part-8/#comment-687</guid>
		<description>Thanks Chris, I actually own that book - suprised? ;-)

Definitely check out Conklin&#039;s stuff, its complimentary yet has little to do with agile as a methodology. His theme is that shared understanding is the root of it all, Agile (and Scrum obviously) happens to have techniques within it that facilitate shared understanding, but there is still a lot of process there and therefore people can get fixated on whether they are following the process right, as opposed to getting everyone on the same page whatever the means...</description>
		<content:encoded><![CDATA[<p>Thanks Chris, I actually own that book &#8211; suprised? <img src='http://www.cleverworkarounds.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Definitely check out Conklin&#8217;s stuff, its complimentary yet has little to do with agile as a methodology. His theme is that shared understanding is the root of it all, Agile (and Scrum obviously) happens to have techniques within it that facilitate shared understanding, but there is still a lot of process there and therefore people can get fixated on whether they are following the process right, as opposed to getting everyone on the same page whatever the means&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
