<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Engineering and Mangement Are Different &#8212; When Will We Learn?</title>
	<link>http://www.reformingprojectmanagement.com/2004/05/02/361/</link>
	<description>The magazine for the project age</description>
	<pubDate>Sun, 12 Oct 2008 19:41:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Hal
        </title>
		<link>http://www.reformingprojectmanagement.com/2004/05/02/361/#comment-211</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2004/05/02/361/#comment-211</guid>
					<description>
        Hi Frank,

I can see how you can think I sing just one note.  I don't argue with your claim that we need better engineering (in some cases).  I claim that too many projects have good engineering at the pieces level without the attention to optimization at the whole.

There are five notes in my song: collaboration, optimization of the whole, increased relatedness of project performers, projects as networks of commitment, and tight coupling of learning with action.  You can make one heck of a melody with just five notes.
      </description>
		<content:encoded><![CDATA[<p>Hi Frank,</p>
<p>I can see how you can think I sing just one note.  I don&#8217;t argue with your claim that we need better engineering (in some cases).  I claim that too many projects have good engineering at the pieces level without the attention to optimization at the whole.</p>
<p>There are five notes in my song: collaboration, optimization of the whole, increased relatedness of project performers, projects as networks of commitment, and tight coupling of learning with action.  You can make one heck of a melody with just five notes.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Frank Winters
        </title>
		<link>http://www.reformingprojectmanagement.com/2004/05/02/361/#comment-212</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2004/05/02/361/#comment-212</guid>
					<description>
        To clarify my point -- while agreeing that the two are different -- we need both improved engineeering and improved management - at the very least.
      </description>
		<content:encoded><![CDATA[<p>To clarify my point &#8212; while agreeing that the two are different &#8212; we need both improved engineeering and improved management - at the very least.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Udi Dahan - The Software Simpl
        </title>
		<link>http://www.reformingprojectmanagement.com/2004/05/02/361/#comment-213</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2004/05/02/361/#comment-213</guid>
					<description>
        Project management is ALL about managing the customer.

Project management is ALL about managing the team.

Project management is HARD.

When there is political in-fighting on the customer side, is it any wonder that engineering can't solve those problems ? When you CAN'T build the right system, does it really matter if you build the system right ?
      </description>
		<content:encoded><![CDATA[<p>Project management is ALL about managing the customer.</p>
<p>Project management is ALL about managing the team.</p>
<p>Project management is HARD.</p>
<p>When there is political in-fighting on the customer side, is it any wonder that engineering can&#8217;t solve those problems ? When you CAN&#8217;T build the right system, does it really matter if you build the system right ?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Frank Winters
        </title>
		<link>http://www.reformingprojectmanagement.com/2004/05/02/361/#comment-214</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2004/05/02/361/#comment-214</guid>
					<description>
        Fitness for purpose is a good engineering principal. If you simply build something well that no one needs you have not engineered the desired/reuired solution.
      </description>
		<content:encoded><![CDATA[<p>Fitness for purpose is a good engineering principal. If you simply build something well that no one needs you have not engineered the desired/reuired solution.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
