<?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: Identifying CAD Project Killers</title>
	<atom:link href="http://www.caddmanager.com/CMB/journals/journal-august-2008/identifying-cad-project-killers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.caddmanager.com/CMB</link>
	<description>Practical, proven insight into CADD Management from Mark W. Kiker</description>
	<lastBuildDate>Wed, 17 Mar 2010 20:13:58 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Carlson</title>
		<link>http://www.caddmanager.com/CMB/journals/journal-august-2008/identifying-cad-project-killers/comment-page-1/#comment-1149</link>
		<dc:creator>John Carlson</dc:creator>
		<pubDate>Thu, 11 Sep 2008 18:21:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.caddmanager.com/CMB/?page_id=636#comment-1149</guid>
		<description>Somewhere between &quot;No Planning&quot; and &quot;Shared between locations&quot; is &quot;Involvment of the other disciplines&quot;  
When working with mulitiple diciplines on a complex project, many things being done in isolation within those teams effect the other disciplines.  Timing is critical, communication is everything.  For instance, moving a building on a site may require different footings from structural.  Failing to tell structural right away may cause huge delays and cost over runs.  Or maybe having structural design the building later in the project eliminates redesign.  I think extensive planning early on and continued involvement of all the disciplines helps elimate profit killers.</description>
		<content:encoded><![CDATA[<p>Somewhere between &#8220;No Planning&#8221; and &#8220;Shared between locations&#8221; is &#8220;Involvment of the other disciplines&#8221;<br />
When working with mulitiple diciplines on a complex project, many things being done in isolation within those teams effect the other disciplines.  Timing is critical, communication is everything.  For instance, moving a building on a site may require different footings from structural.  Failing to tell structural right away may cause huge delays and cost over runs.  Or maybe having structural design the building later in the project eliminates redesign.  I think extensive planning early on and continued involvement of all the disciplines helps elimate profit killers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don Standish</title>
		<link>http://www.caddmanager.com/CMB/journals/journal-august-2008/identifying-cad-project-killers/comment-page-1/#comment-866</link>
		<dc:creator>Don Standish</dc:creator>
		<pubDate>Thu, 28 Aug 2008 13:15:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.caddmanager.com/CMB/?page_id=636#comment-866</guid>
		<description>How about Profit Killers for a title instead.</description>
		<content:encoded><![CDATA[<p>How about Profit Killers for a title instead.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CADDManager</title>
		<link>http://www.caddmanager.com/CMB/journals/journal-august-2008/identifying-cad-project-killers/comment-page-1/#comment-828</link>
		<dc:creator>CADDManager</dc:creator>
		<pubDate>Tue, 19 Aug 2008 19:51:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.caddmanager.com/CMB/?page_id=636#comment-828</guid>
		<description>Project Killers is strong language and I agree that it would take a lot more than these to actually &quot;terminate&quot; a project...

But the title was too good to pass up :)

Mark</description>
		<content:encoded><![CDATA[<p>Project Killers is strong language and I agree that it would take a lot more than these to actually &#8220;terminate&#8221; a project&#8230;</p>
<p>But the title was too good to pass up <img src='http://www.caddmanager.com/CMB/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Mark</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Patterson</title>
		<link>http://www.caddmanager.com/CMB/journals/journal-august-2008/identifying-cad-project-killers/comment-page-1/#comment-826</link>
		<dc:creator>Jim Patterson</dc:creator>
		<pubDate>Tue, 19 Aug 2008 14:51:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.caddmanager.com/CMB/?page_id=636#comment-826</guid>
		<description>Project Killers?  I think you want to say Project Delayers, the only one that can kill a project is the owner or client.  What you discribe are just problems of everyday work flow.</description>
		<content:encoded><![CDATA[<p>Project Killers?  I think you want to say Project Delayers, the only one that can kill a project is the owner or client.  What you discribe are just problems of everyday work flow.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
