<?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: Reliable Promising and Lean Approach Gets the Job Done</title>
	<link>http://www.reformingprojectmanagement.com/2002/12/16/76/</link>
	<description>The magazine for the project age</description>
	<pubDate>Thu, 07 Aug 2008 22:44:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Joe Ely
        </title>
		<link>http://www.reformingprojectmanagement.com/2002/12/16/76/#comment-428</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2002/12/16/76/#comment-428</guid>
					<description>
        Hal, this type of observation of effective practice is very helpful.  Could you expand on your observations with further entries in the web log over the next few days??  

Tks

Joe
      </description>
		<content:encoded><![CDATA[<p>Hal, this type of observation of effective practice is very helpful.  Could you expand on your observations with further entries in the web log over the next few days??  </p>
<p>Tks</p>
<p>Joe
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Chris Tulino
        </title>
		<link>http://www.reformingprojectmanagement.com/2002/12/16/76/#comment-429</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2002/12/16/76/#comment-429</guid>
					<description>
        I had forgotten all about the use of pareto charts.  Tracking the reasons for plan variance seems to be an excellent way to determine where the project lacks the ability to stick to the plan, either due to execution problems, or planning problems.
      </description>
		<content:encoded><![CDATA[<p>I had forgotten all about the use of pareto charts.  Tracking the reasons for plan variance seems to be an excellent way to determine where the project lacks the ability to stick to the plan, either due to execution problems, or planning problems.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Hal
        </title>
		<link>http://www.reformingprojectmanagement.com/2002/12/16/76/#comment-430</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2002/12/16/76/#comment-430</guid>
					<description>
        Tracking reasons for plan failure has been a very useful practice for improving project reliability.  The pareto chart offers the team the opportunity to focus on the big hitters or get help from management on issues more systemic in nature.  Time and time again we find the principal reasons recorded to be in the control of the project team.  Start recording plan failures on your project if for no other reason than to have the team discover they can take full charge of their projects.

p.s.  Joe, I will make more observations and comments on effective practice.  Thanks for the suggestion.  :+:
      </description>
		<content:encoded><![CDATA[<p>Tracking reasons for plan failure has been a very useful practice for improving project reliability.  The pareto chart offers the team the opportunity to focus on the big hitters or get help from management on issues more systemic in nature.  Time and time again we find the principal reasons recorded to be in the control of the project team.  Start recording plan failures on your project if for no other reason than to have the team discover they can take full charge of their projects.</p>
<p>p.s.  Joe, I will make more observations and comments on effective practice.  Thanks for the suggestion.  :+:
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
