<?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: Lastest Discussion of 8th Waste</title>
	<atom:link href="http://www.reformingprojectmanagement.com/2008/08/24/875/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.reformingprojectmanagement.com/2008/08/24/875/</link>
	<description>The magazine for the project age</description>
	<lastBuildDate>Fri, 15 Apr 2011 17:20:14 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jim Young</title>
		<link>http://www.reformingprojectmanagement.com/2008/08/24/875/comment-page-1/#comment-20786</link>
		<dc:creator>Jim Young</dc:creator>
		<pubDate>Thu, 23 Oct 2008 14:34:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/2008/08/24/875/#comment-20786</guid>
		<description>I&#039;m late to this conversation, but our project work (hospital facility creation) has led us to understand that the 8th waste is more than re-creation of knowledge, it is the pure wasted opportunity to harvest all the IQ points around the table by enagaging all the brains on every project issue they&#039;d like to weigh in on.  Real-time conversational process...</description>
		<content:encoded><![CDATA[<p>I&#8217;m late to this conversation, but our project work (hospital facility creation) has led us to understand that the 8th waste is more than re-creation of knowledge, it is the pure wasted opportunity to harvest all the IQ points around the table by enagaging all the brains on every project issue they&#8217;d like to weigh in on.  Real-time conversational process&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Animesh Mehra</title>
		<link>http://www.reformingprojectmanagement.com/2008/08/24/875/comment-page-1/#comment-20785</link>
		<dc:creator>Animesh Mehra</dc:creator>
		<pubDate>Tue, 14 Oct 2008 08:45:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/2008/08/24/875/#comment-20785</guid>
		<description>Couldn&#039;t agree more. Our management model in fact would prevent &quot;reinventing the wheel&quot; wastes to accumulate over time. Re-use is the key that we are going to follow in future.</description>
		<content:encoded><![CDATA[<p>Couldn&#8217;t agree more. Our management model in fact would prevent &#8220;reinventing the wheel&#8221; wastes to accumulate over time. Re-use is the key that we are going to follow in future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Green</title>
		<link>http://www.reformingprojectmanagement.com/2008/08/24/875/comment-page-1/#comment-20779</link>
		<dc:creator>David Green</dc:creator>
		<pubDate>Thu, 11 Sep 2008 03:39:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/2008/08/24/875/#comment-20779</guid>
		<description>I think one of the sources of these great wastes, and not only in construction, is the way &#039;project&#039; has been traditionally defined. As I compare what is typically written about project management, and compare it with what is being written about management in general, I find that PM seems often to be about 5 decades behind! It often adopts a mechanistic command and control approach, with &#039;management by objectives&#039; limitations that disparage the contributions of &#039;doers&#039; to find improvement opportunities and adopt them and can disinvolve those with either actual or operational expertise.

So, how to define a &#039;project&#039; to perhaps avoid this? Here&#039;s my attempt:

A project occurs when people act together (make commitments) to invest their effort to produce a benefit or value in response to environmental flux (that is, changes in the relationships within the organisation&#039;s network) or emergent opportunities.

This separates projects from &#039;normal operations&#039; which occur with the general presumtion of environmental constancy, as in a production line, for intance, and locates a project in the interactions of an organisation and its business context; for instance, where a client sees a development opporutnity and ask for an effort to realise that opportunity.</description>
		<content:encoded><![CDATA[<p>I think one of the sources of these great wastes, and not only in construction, is the way &#8216;project&#8217; has been traditionally defined. As I compare what is typically written about project management, and compare it with what is being written about management in general, I find that PM seems often to be about 5 decades behind! It often adopts a mechanistic command and control approach, with &#8216;management by objectives&#8217; limitations that disparage the contributions of &#8216;doers&#8217; to find improvement opportunities and adopt them and can disinvolve those with either actual or operational expertise.</p>
<p>So, how to define a &#8216;project&#8217; to perhaps avoid this? Here&#8217;s my attempt:</p>
<p>A project occurs when people act together (make commitments) to invest their effort to produce a benefit or value in response to environmental flux (that is, changes in the relationships within the organisation&#8217;s network) or emergent opportunities.</p>
<p>This separates projects from &#8216;normal operations&#8217; which occur with the general presumtion of environmental constancy, as in a production line, for intance, and locates a project in the interactions of an organisation and its business context; for instance, where a client sees a development opporutnity and ask for an effort to realise that opportunity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Ely</title>
		<link>http://www.reformingprojectmanagement.com/2008/08/24/875/comment-page-1/#comment-20777</link>
		<dc:creator>Joe Ely</dc:creator>
		<pubDate>Thu, 28 Aug 2008 19:57:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/2008/08/24/875/#comment-20777</guid>
		<description>Hal, you connect two very important dots here.

One is the Great Wastes.  It captures much, this tendency to not speak, this proclivity to not listen.  

The second dot are the countermeasures to this waste:  attention, consensus.  I would add use of Socratic Method to involve others in learning.  

Seeing the Waste and applying the countermeasures, relentlessly, is what us Lean Leaders need to do.

Thanks for the post.</description>
		<content:encoded><![CDATA[<p>Hal, you connect two very important dots here.</p>
<p>One is the Great Wastes.  It captures much, this tendency to not speak, this proclivity to not listen.  </p>
<p>The second dot are the countermeasures to this waste:  attention, consensus.  I would add use of Socratic Method to involve others in learning.  </p>
<p>Seeing the Waste and applying the countermeasures, relentlessly, is what us Lean Leaders need to do.</p>
<p>Thanks for the post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lech</title>
		<link>http://www.reformingprojectmanagement.com/2008/08/24/875/comment-page-1/#comment-20776</link>
		<dc:creator>Lech</dc:creator>
		<pubDate>Wed, 27 Aug 2008 06:20:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/2008/08/24/875/#comment-20776</guid>
		<description>Convincing! &quot;Recreating knowledge&quot; definitely deserves a place on the list. It&#039;s more general than &quot;not listening&quot; and &quot;not speaking&quot;. Both of them seem to boil down to communication issues (risk) or lack of efficient communication altogether. However, there is more to it than sharing information. After all, process improvement is about learning and using that knowledge once and for all, isn&#039;t it?</description>
		<content:encoded><![CDATA[<p>Convincing! &#8220;Recreating knowledge&#8221; definitely deserves a place on the list. It&#8217;s more general than &#8220;not listening&#8221; and &#8220;not speaking&#8221;. Both of them seem to boil down to communication issues (risk) or lack of efficient communication altogether. However, there is more to it than sharing information. After all, process improvement is about learning and using that knowledge once and for all, isn&#8217;t it?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 1.151 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2011-08-22 07:21:24 -->

