<?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: Best Practices for Managing  Successful Projects</title>
	<link>http://www.reformingprojectmanagement.com/2006/10/31/678/</link>
	<description>The magazine for the project age</description>
	<pubDate>Thu, 20 Nov 2008 22:41:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Glen B Alleman</title>
		<link>http://www.reformingprojectmanagement.com/2006/10/31/678/#comment-10908</link>
		<pubDate>Wed, 01 Nov 2006 22:10:16 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2006/10/31/678/#comment-10908</guid>
					<description>Hal,

Thanks for the recommendation. This sounds much like the IMP/IMS (Integrated Master Plan / Integrated Master Schedule) approach where the "Plan" represents the increasing maturity of the project in terms of the customers expectations. The "roadmap" is the path through the Significant Accomplishments that deliver inceasing value (maturity) from the efforts of the project team. Accomplishment Criteria are the "exit criteria" for the tasks that deliver the work in fulfillment of the Signifiant Accomplishments.

The IMP/IMS approach has many other attributes inappropriate for IT or non-defense projects, but the principles of defining the customer's criteria for assesing value delivery, measuring that value in units useful to the customer and having an Integrated Product Team (IPT) - meaning everyone is on the team and has skin in the game - is the basis of many succesful defense contracts - including a few I've planned and particapated in</description>
		<content:encoded><![CDATA[<p>Hal,</p>
<p>Thanks for the recommendation. This sounds much like the IMP/IMS (Integrated Master Plan / Integrated Master Schedule) approach where the &#8220;Plan&#8221; represents the increasing maturity of the project in terms of the customers expectations. The &#8220;roadmap&#8221; is the path through the Significant Accomplishments that deliver inceasing value (maturity) from the efforts of the project team. Accomplishment Criteria are the &#8220;exit criteria&#8221; for the tasks that deliver the work in fulfillment of the Signifiant Accomplishments.</p>
<p>The IMP/IMS approach has many other attributes inappropriate for IT or non-defense projects, but the principles of defining the customer&#8217;s criteria for assesing value delivery, measuring that value in units useful to the customer and having an Integrated Product Team (IPT) - meaning everyone is on the team and has skin in the game - is the basis of many succesful defense contracts - including a few I&#8217;ve planned and particapated in
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dan</title>
		<link>http://www.reformingprojectmanagement.com/2006/10/31/678/#comment-10896</link>
		<pubDate>Wed, 01 Nov 2006 14:22:21 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2006/10/31/678/#comment-10896</guid>
					<description>Great entry, and great blog! I'm the Editor-in-Chief of RogueProjectLeader.com, and wish I'd come across your site sooner (RPL is currently on a hiatus, but you might find some interesting things in our archive).

Will have to check out Rainbows &#38; Ratholes - thanks for the intro!</description>
		<content:encoded><![CDATA[<p>Great entry, and great blog! I&#8217;m the Editor-in-Chief of RogueProjectLeader.com, and wish I&#8217;d come across your site sooner (RPL is currently on a hiatus, but you might find some interesting things in our archive).</p>
<p>Will have to check out Rainbows &amp; Ratholes - thanks for the intro!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
