<?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 Has the Gantt Chart Done for You Lately?</title>
	<link>http://www.reformingprojectmanagement.com/2007/01/07/730/</link>
	<description>The magazine for the project age</description>
	<pubDate>Sun, 20 Jul 2008 18:33:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Glen John-Lewis</title>
		<link>http://www.reformingprojectmanagement.com/2007/01/07/730/#comment-12410</link>
		<pubDate>Sat, 13 Jan 2007 20:01:33 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2007/01/07/730/#comment-12410</guid>
					<description>I agree with Diane H, the gantt provides the team with the bigger picture, but also they can read how crucial and important their responsibility is to the delivery of their tasks. I understand that to be able to recognise the urgency of the tasks they need to be able to understand and analyise a gantt. This is where the PM comes in, delivering updates and progress reports at team briefings and discussing where at crucial points they fit in.
Glen.</description>
		<content:encoded><![CDATA[<p>I agree with Diane H, the gantt provides the team with the bigger picture, but also they can read how crucial and important their responsibility is to the delivery of their tasks. I understand that to be able to recognise the urgency of the tasks they need to be able to understand and analyise a gantt. This is where the PM comes in, delivering updates and progress reports at team briefings and discussing where at crucial points they fit in.<br />
Glen.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Glen B Alleman</title>
		<link>http://www.reformingprojectmanagement.com/2007/01/07/730/#comment-12331</link>
		<pubDate>Tue, 09 Jan 2007 15:36:01 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2007/01/07/730/#comment-12331</guid>
					<description>Hal,

The Gantt chart is useful IIF it can show the right things to the right people

1. There are no widows or orphans in the underlying network and there are not hard constraints - this provides confidence that the Gannt chart represents the underlying work in a credible manner - not fixed starts or end. If there are such things, then the Gantt is noting more than a Power Point presentation of the plan
2. Same goes for the resource loading

What I've found most useful is a Gannt that represents the increasing maturity of the project through Work Packages that show deliverables. The IMP/IMS style is another approach but is sometimes too complex.

In both cases the Gantt should be seen or read as a Statement of Work for the project, with past tense verbs at the summary bars and present tense verbs at the lowest task level. 

Style seems to be important, so using color and bar styles to draw attention to the important activities helps. Tuftes (sic) has a hanging Gantt style which is very similar to the Critical Tools PERT Chart Expert style used in aerospace and large construction. 

The Gantt though is just a representation of the underlying network. The integrity of the Gantt starts with the network integrity.

Other tools we use include FastTrack 9.0 and Visio at times</description>
		<content:encoded><![CDATA[<p>Hal,</p>
<p>The Gantt chart is useful IIF it can show the right things to the right people</p>
<p>1. There are no widows or orphans in the underlying network and there are not hard constraints - this provides confidence that the Gannt chart represents the underlying work in a credible manner - not fixed starts or end. If there are such things, then the Gantt is noting more than a Power Point presentation of the plan<br />
2. Same goes for the resource loading</p>
<p>What I&#8217;ve found most useful is a Gannt that represents the increasing maturity of the project through Work Packages that show deliverables. The IMP/IMS style is another approach but is sometimes too complex.</p>
<p>In both cases the Gantt should be seen or read as a Statement of Work for the project, with past tense verbs at the summary bars and present tense verbs at the lowest task level. </p>
<p>Style seems to be important, so using color and bar styles to draw attention to the important activities helps. Tuftes (sic) has a hanging Gantt style which is very similar to the Critical Tools PERT Chart Expert style used in aerospace and large construction. </p>
<p>The Gantt though is just a representation of the underlying network. The integrity of the Gantt starts with the network integrity.</p>
<p>Other tools we use include FastTrack 9.0 and Visio at times
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Diana Hutchinson</title>
		<link>http://www.reformingprojectmanagement.com/2007/01/07/730/#comment-12327</link>
		<pubDate>Tue, 09 Jan 2007 15:20:59 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2007/01/07/730/#comment-12327</guid>
					<description>A Gantt chart is a valuable tool for giving the team and management a big picture view.  On projects when I haven't used one starting out, I find the team members struggle without a framework, and this helps get in sync.  
The other benefit is using the critical path to identify for the project manager and the team which part of the tasks need to be done as soon as possible in order to minimize overall project time, and which ones could be slipped to accommodate other project needs or resource limitations.
I have also found the Visio timeline to be a useful tool in showing the big picture project phases for the team and management.</description>
		<content:encoded><![CDATA[<p>A Gantt chart is a valuable tool for giving the team and management a big picture view.  On projects when I haven&#8217;t used one starting out, I find the team members struggle without a framework, and this helps get in sync.<br />
The other benefit is using the critical path to identify for the project manager and the team which part of the tasks need to be done as soon as possible in order to minimize overall project time, and which ones could be slipped to accommodate other project needs or resource limitations.<br />
I have also found the Visio timeline to be a useful tool in showing the big picture project phases for the team and management.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dr. Jerry Mulenburg</title>
		<link>http://www.reformingprojectmanagement.com/2007/01/07/730/#comment-12321</link>
		<pubDate>Mon, 08 Jan 2007 23:25:18 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2007/01/07/730/#comment-12321</guid>
					<description>I'm sure others have found and probably mentioned the same experience that I have in relating project information. This is, the higer up you go, the simpler the communication must be. 

In discussing a project with your peers (e.g. other project managers) you need to provide technical detail and can show them the project plan, the schedule, WBS, risk list, etc. and they get a good sense of what you are talking about. First level management needs, and wants, much less detail: how far you are ahead of or behind on schedule, cost, and what problems you are having. As you go further up the chain, the detail must be shredded out until, when you talk to the highest management levels, a cartoon will usually do just fine.

The Gantt chart is not much more than a cartoon for management and other stakeholders to understand what you're doing and how you're progressing. In this sense, it may be one of the most valuable tools in your kit.</description>
		<content:encoded><![CDATA[<p>I&#8217;m sure others have found and probably mentioned the same experience that I have in relating project information. This is, the higer up you go, the simpler the communication must be. </p>
<p>In discussing a project with your peers (e.g. other project managers) you need to provide technical detail and can show them the project plan, the schedule, <acronym title="Work Breakdown Structure; a way of bringing organization to the description and categories of work in a project">WBS</acronym>, risk list, etc. and they get a good sense of what you are talking about. First level management needs, and wants, much less detail: how far you are ahead of or behind on schedule, cost, and what problems you are having. As you go further up the chain, the detail must be shredded out until, when you talk to the highest management levels, a cartoon will usually do just fine.</p>
<p>The Gantt chart is not much more than a cartoon for management and other stakeholders to understand what you&#8217;re doing and how you&#8217;re progressing. In this sense, it may be one of the most valuable tools in your kit.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Chet Frame</title>
		<link>http://www.reformingprojectmanagement.com/2007/01/07/730/#comment-12314</link>
		<pubDate>Mon, 08 Jan 2007 15:42:27 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2007/01/07/730/#comment-12314</guid>
					<description>I think that the Gantt Chart is a pretty good communication device between the Project Manager and his team and the Steering Committee.  It does provide some meaure of a "to do" list, but it is a fairly clear representation of what you thought you were going to do, what you've done, and what more has to be done to meet your original plan.</description>
		<content:encoded><![CDATA[<p>I think that the Gantt Chart is a pretty good communication device between the Project Manager and his team and the Steering Committee.  It does provide some meaure of a &#8220;to do&#8221; list, but it is a fairly clear representation of what you thought you were going to do, what you&#8217;ve done, and what more has to be done to meet your original plan.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
