<?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: Don&#8217;t Give Up on Gantt Charts Yet</title>
	<link>http://www.reformingprojectmanagement.com/2007/01/10/735/</link>
	<description>The magazine for the project age</description>
	<pubDate>Wed, 08 Oct 2008 08:31:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Glen B. Alleman</title>
		<link>http://www.reformingprojectmanagement.com/2007/01/10/735/#comment-12402</link>
		<pubDate>Sat, 13 Jan 2007 07:12:59 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2007/01/10/735/#comment-12402</guid>
					<description>David,

Add to the bottom of the Gantt the Earned Value numbers as described in any EIA-748-B and DOD Earned Value training guide and you'll have solved this problem in the way $100B of development projects do every year in the defense industry.

All those performance problems you've described above are domain independent and occur everywhere I've managed projects - software, hardware, environmental, operations... Defining accountability, identifying personal and team performance and identifying the deliverables, capabilities and outcomes in the Plan is the starting point. The schedule is NOT the Plan though. The Plan is the strategy for delivering the value to the stakeholder. The current approach in many industries is to employee the IMP/IMS (Integrated Master Plan / Integrated Master Schedule) paradigm, along with Capabilities Based Planning to discover what is it we'd like the participants to be accountable for other than spending money and passing time

Links to this approach available on request...</description>
		<content:encoded><![CDATA[<p>David,</p>
<p>Add to the bottom of the Gantt the Earned Value numbers as described in any EIA-748-B and DOD Earned Value training guide and you&#8217;ll have solved this problem in the way $100B of development projects do every year in the defense industry.</p>
<p>All those performance problems you&#8217;ve described above are domain independent and occur everywhere I&#8217;ve managed projects - software, hardware, environmental, operations&#8230; Defining accountability, identifying personal and team performance and identifying the deliverables, capabilities and outcomes in the Plan is the starting point. The schedule is NOT the Plan though. The Plan is the strategy for delivering the value to the stakeholder. The current approach in many industries is to employee the IMP/IMS (Integrated Master Plan / Integrated Master Schedule) paradigm, along with Capabilities Based Planning to discover what is it we&#8217;d like the participants to be accountable for other than spending money and passing time</p>
<p>Links to this approach available on request&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: David Geren</title>
		<link>http://www.reformingprojectmanagement.com/2007/01/10/735/#comment-12388</link>
		<pubDate>Thu, 11 Jan 2007 22:15:13 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2007/01/10/735/#comment-12388</guid>
					<description>My experience is that Gantt charts (or network charts) give the impression of communiciation, but do not provide useful management content or enable decision making; so they appear to inform, but in fact provide no real report.
I think that meaningful project reports are about the target and predicted dates of milestones. For our projects we set up milestones: important project events, such as completing a deliverable, or a major work component leading to a deliverable, and set target dates for them. Then we ask project managers to provide 'predicted' dates for each milestone. The predicted date is the date they really think the milestone event will occur on. The prediction must flow on to subsequent milestones and the completion date: negotiation takes place then on resources, or obtaining agreement to date changes. PMs are tracked on their milestone delivery performance, acknowledging that slippage is usually an organisational problem, not an individual's under-performance.</description>
		<content:encoded><![CDATA[<p>My experience is that Gantt charts (or network charts) give the impression of communiciation, but do not provide useful management content or enable decision making; so they appear to inform, but in fact provide no real report.<br />
I think that meaningful project reports are about the target and predicted dates of milestones. For our projects we set up milestones: important project events, such as completing a deliverable, or a major work component leading to a deliverable, and set target dates for them. Then we ask project managers to provide &#8216;predicted&#8217; dates for each milestone. The predicted date is the date they really think the milestone event will occur on. The prediction must flow on to subsequent milestones and the completion date: negotiation takes place then on resources, or obtaining agreement to date changes. PMs are tracked on their milestone delivery performance, acknowledging that slippage is usually an organisational problem, not an individual&#8217;s under-performance.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
