Prev: Gant Chart Freeze Panes
Next: Sychronise the microsoft project calendar to our calendar
From: salgud on 23 Mar 2010 09:44
On Mon, 22 Mar 2010 18:29:19 +0430, Nooneami wrote:

> On Mon, 22 Mar 2010 07:54:06 -0600, salgud <spamboy6547(a)comcast.net>
> wrote:
>
>>On Mon, 22 Mar 2010 18:16:39 +0430, Nooneami wrote:
>>>
>>> I have a simple project where the first task takes 28 edays
>>
>>Project doesn't have the ability to create a non-linear time line as you
>>would like. Kind of defeats the main purpose of the Gantt, to show the time
>>each task takes.
>>
>>Also, there is a guideline in Project Management that says all tasks should
>>have durations between 1 and 10 days. All of your tasks excede that, which
>>will leave you very vulnerable to slipping the project a significant amount
>>without knowing it until it has happened. Breaking the tasks down into
>>shorter tasks of less than 10 days would give you a much greater
>>probability of completing your project on time.
>>
>>Hope this helps.
>
> It certainly stops me wasting time trying to find a solution - Much
> appreciated.
>
> The first task is component delivery time - not much to do about that.
> The reason for keeping that in the program is that it shows the client
> that the works cannot commence untill the components are delivered.
>
> But again - thanks.
>
> Moeller

Then, do as Mike suggests, make it a milestone.

Or, better yet, have your vendor report progress over the 28 days, in some
way which can be verified. That way, if they slip, you'll know it BEFORE
it's 28 days late. Make inspection trips, ask for photos of progress, if
applicable, etc.
First  |  Prev  | 
Pages: 1 2
Prev: Gant Chart Freeze Panes
Next: Sychronise the microsoft project calendar to our calendar