Prev: Gant Chart Freeze Panes
Next: Sychronise the microsoft project calendar to our calendar
From: Nooneami on 22 Mar 2010 09:46
Hi,

I have a simple project where the first task takes 28 edays and the
following 36 tasks takes 13 days. Is there any way to break up the
timeline to that rather than showing 6 weeks (say six inches on paper)
of equal length so to speak it, instead show the first 4 weeks as one
inch and the remainder as five inches?

Hope I made it clear what I want to do.

Thanks

Moeller
From: salgud on 22 Mar 2010 09:54
On Mon, 22 Mar 2010 18:16:39 +0430, Nooneami wrote:

> Hi,
>
> I have a simple project where the first task takes 28 edays and the
> following 36 tasks takes 13 days. Is there any way to break up the
> timeline to that rather than showing 6 weeks (say six inches on paper)
> of equal length so to speak it, instead show the first 4 weeks as one
> inch and the remainder as five inches?
>
> Hope I made it clear what I want to do.
>
> Thanks
>
> Moeller

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.
From: Jan De Messemaeker on 22 Mar 2010 09:57
Hi,

Very clear indeed, but sorry, this is not possible.

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf
"Nooneami" <s(a)m.n> wrote in message
news:htseq5hgtm97hpepgsc9f3lnakehjkm79e(a)4ax.com...
> Hi,
>
> I have a simple project where the first task takes 28 edays and the
> following 36 tasks takes 13 days. Is there any way to break up the
> timeline to that rather than showing 6 weeks (say six inches on paper)
> of equal length so to speak it, instead show the first 4 weeks as one
> inch and the remainder as five inches?
>
> Hope I made it clear what I want to do.
>
> Thanks
>
> Moeller


From: Nooneami on 22 Mar 2010 09:59
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
From: Andrew Lavinsky on 22 Mar 2010 19:19
3rd party reporting apps may be able to do this....


- Andrew Lavinsky
Blog: http://blogs.catapultsystems.com/epm

> 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
>


 |  Next  |  Last
Pages: 1 2
Prev: Gant Chart Freeze Panes
Next: Sychronise the microsoft project calendar to our calendar