<?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: What&#8217;s Driving Toyota?</title>
	<link>http://www.reformingprojectmanagement.com/2006/09/25/665/</link>
	<description>The magazine for the project age</description>
	<pubDate>Fri, 16 May 2008 22:33:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Phil Rutherford</title>
		<link>http://www.reformingprojectmanagement.com/2006/09/25/665/#comment-10188</link>
		<pubDate>Tue, 26 Sep 2006 07:39:24 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2006/09/25/665/#comment-10188</guid>
					<description>I actually read the article slightly differently and in doing so was reminded of my time in the military. There we would make sure that everybody knew not just what their job was but what everybody else was supposed to be doing as well. Then these roles would be practised - the degree of practise depending upon the degree of complexity or asymmetry that was expected during the actual manouevre or operation. A highly complex or asymmetric manouevre demanded a great deal of practise at individual and group roles, a less complex one demanding not as much.

I've often wondered how this would go in the world of project management. I know in my own projects I've always made sure we rehearsed elements that were expected to be complex or fraught with risks but have never heard of anybody else doing this. Do any members of this group know how widespread such an approach to complex or asymmetric projects is?</description>
		<content:encoded><![CDATA[<p>I actually read the article slightly differently and in doing so was reminded of my time in the military. There we would make sure that everybody knew not just what their job was but what everybody else was supposed to be doing as well. Then these roles would be practised - the degree of practise depending upon the degree of complexity or asymmetry that was expected during the actual manouevre or operation. A highly complex or asymmetric manouevre demanded a great deal of practise at individual and group roles, a less complex one demanding not as much.</p>
<p>I&#8217;ve often wondered how this would go in the world of project management. I know in my own projects I&#8217;ve always made sure we rehearsed elements that were expected to be complex or fraught with risks but have never heard of anybody else doing this. Do any members of this group know how widespread such an approach to complex or asymmetric projects is?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Joe Ely</title>
		<link>http://www.reformingprojectmanagement.com/2006/09/25/665/#comment-10178</link>
		<pubDate>Mon, 25 Sep 2006 18:39:17 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2006/09/25/665/#comment-10178</guid>
					<description>excellent article and summary of TPS from a non-manufacturing perspective, Hal, thanks for linking to it.  very interesting how they did kaizen with dealers in developing a web-based ordering system.

The philosophy works...just keep applying it.  It is the perseverence that is the key.</description>
		<content:encoded><![CDATA[<p>excellent article and summary of TPS from a non-manufacturing perspective, Hal, thanks for linking to it.  very interesting how they did <acronym title="Japanese term for continuous improvement">kaizen</acronym> with dealers in developing a web-based ordering system.</p>
<p>The philosophy works&#8230;just keep applying it.  It is the perseverence that is the key.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
