Prev: importing schedule into outlook calendar
Next: Microsoft Office has identified a potential security concern
From: Project Manager on 26 Mar 2010 16:40
I'm getting a zig zag at the top of my progress line even though it is set to
show the current date. It is starting the progress line at the original
proejct date and then zig zagging the line to the current date. How do i fix
this?
From: Rod Gill on 26 Mar 2010 21:33
My best practices suggest to never ever use progress lines. Better to update
actual start and finish dates and rely on baseline data to show where you
should have been using the Tracking Gantt chart.

Progress lines cause problems, because you have incomplete work in the past
and completed work in the future. How do you determine what your project's
resource needs are for the next few weeks?

By updating as recommended above, all work for next week needs to be done
and all work for last week is complete (provided you have also moved all
incomplete work out to next week after updating your schedule).

Good luck!

--

Rod Gill
Microsoft MVP for Project - http://www.project-systems.co.nz

Author of the only book on Project VBA, see: http://www.projectvbabook.com




"Project Manager" <ProjectManager(a)discussions.microsoft.com> wrote in
message news:291804E1-5D0D-4879-8D3C-8C29DE5586D6(a)microsoft.com...
> I'm getting a zig zag at the top of my progress line even though it is set
> to
> show the current date. It is starting the progress line at the original
> proejct date and then zig zagging the line to the current date. How do i
> fix
> this?
>
> __________ Information from ESET Smart Security, version of virus
> signature database 4978 (20100326) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
>

__________ Information from ESET Smart Security, version of virus signature database 4978 (20100326) __________

The message was checked by ESET Smart Security.

http://www.eset.com



From: Project Manager on 28 Mar 2010 16:46
I don't use the progress lines to indicate what work is done and what work
needs to be completed. I use it as an indication of generally where we are
on a schedule. I have a lot of customer's who don't know how to read a
project schedule, but because of the work and coordination (as managers of a
design process) we need to have one.

so.... this progress line helps my customer to quickly identify on our
project schedule were we are.

still searching for an answer.

"Rod Gill" wrote:

> My best practices suggest to never ever use progress lines. Better to update
> actual start and finish dates and rely on baseline data to show where you
> should have been using the Tracking Gantt chart.
>
> Progress lines cause problems, because you have incomplete work in the past
> and completed work in the future. How do you determine what your project's
> resource needs are for the next few weeks?
>
> By updating as recommended above, all work for next week needs to be done
> and all work for last week is complete (provided you have also moved all
> incomplete work out to next week after updating your schedule).
>
> Good luck!
>
> --
>
> Rod Gill
> Microsoft MVP for Project - http://www.project-systems.co.nz
>
> Author of the only book on Project VBA, see: http://www.projectvbabook.com
>
>
>
>
> "Project Manager" <ProjectManager(a)discussions.microsoft.com> wrote in
> message news:291804E1-5D0D-4879-8D3C-8C29DE5586D6(a)microsoft.com...
> > I'm getting a zig zag at the top of my progress line even though it is set
> > to
> > show the current date. It is starting the progress line at the original
> > proejct date and then zig zagging the line to the current date. How do i
> > fix
> > this?
> >
> > __________ Information from ESET Smart Security, version of virus
> > signature database 4978 (20100326) __________
> >
> > The message was checked by ESET Smart Security.
> >
> > http://www.eset.com
> >
> >
> >
>
> __________ Information from ESET Smart Security, version of virus signature database 4978 (20100326) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
>
> .
>
From: Rod Gill on 28 Mar 2010 20:59
If the project is updated properly, you are always on today's date: late
work delayed until it restarts, early work pulled forward to when it
actually started, hence progress line redundant.

--

Rod Gill
Microsoft MVP for Project - http://www.project-systems.co.nz

Author of the only book on Project VBA, see: http://www.projectvbabook.com




"Project Manager" <ProjectManager(a)discussions.microsoft.com> wrote in
message news:9AD1E9BC-3C1E-4A71-8FFA-E9B4AEF6140F(a)microsoft.com...
> I don't use the progress lines to indicate what work is done and what work
> needs to be completed. I use it as an indication of generally where we
> are
> on a schedule. I have a lot of customer's who don't know how to read a
> project schedule, but because of the work and coordination (as managers of
> a
> design process) we need to have one.
>
> so.... this progress line helps my customer to quickly identify on our
> project schedule were we are.
>
> still searching for an answer.
>
> "Rod Gill" wrote:
>
>> My best practices suggest to never ever use progress lines. Better to
>> update
>> actual start and finish dates and rely on baseline data to show where you
>> should have been using the Tracking Gantt chart.
>>
>> Progress lines cause problems, because you have incomplete work in the
>> past
>> and completed work in the future. How do you determine what your
>> project's
>> resource needs are for the next few weeks?
>>
>> By updating as recommended above, all work for next week needs to be done
>> and all work for last week is complete (provided you have also moved all
>> incomplete work out to next week after updating your schedule).
>>
>> Good luck!
>>
>> --
>>
>> Rod Gill
>> Microsoft MVP for Project - http://www.project-systems.co.nz
>>
>> Author of the only book on Project VBA, see:
>> http://www.projectvbabook.com
>>
>>
>>
>>
>> "Project Manager" <ProjectManager(a)discussions.microsoft.com> wrote in
>> message news:291804E1-5D0D-4879-8D3C-8C29DE5586D6(a)microsoft.com...
>> > I'm getting a zig zag at the top of my progress line even though it is
>> > set
>> > to
>> > show the current date. It is starting the progress line at the original
>> > proejct date and then zig zagging the line to the current date. How do
>> > i
>> > fix
>> > this?
>> >
>> > __________ Information from ESET Smart Security, version of virus
>> > signature database 4978 (20100326) __________
>> >
>> > The message was checked by ESET Smart Security.
>> >
>> > http://www.eset.com
>> >
>> >
>> >
>>
>> __________ Information from ESET Smart Security, version of virus
>> signature database 4978 (20100326) __________
>>
>> The message was checked by ESET Smart Security.
>>
>> http://www.eset.com
>>
>>
>>
>> .
>>
>
> __________ Information from ESET Smart Security, version of virus
> signature database 4980 (20100328) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
>

__________ Information from ESET Smart Security, version of virus signature database 4980 (20100328) __________

The message was checked by ESET Smart Security.

http://www.eset.com



From: Trevor Rabey on 28 Mar 2010 23:42
What does the zig-zag progress line show the client, what information does
it convey, and how does it help him to see the progress lines?
If it zigs to the left, it indivates that you have a planned task in the
past. Since you cannot plan to do something in the past, this only indicates
that you have not updated the plan properly.
If it zags to the right, this indicates that you have shown progress in the
future. Since you cannot achieve progress in the future, this only indicates
that you have not updated the plan properly.

Although the progress lines may be useful to you to see where you have not
updated the plan properly, I would not put anything with zig-zags in front
of a client.
Of course, your client probably won't know what they are looking at so it
probably won't matter if you do.
--
Trevor Rabey
0407213955
61 8 92727485
PERFECT PROJECT PLANNING
www.perfectproject.com.au

"Project Manager" <ProjectManager(a)discussions.microsoft.com> wrote in
message news:9AD1E9BC-3C1E-4A71-8FFA-E9B4AEF6140F(a)microsoft.com...
>I don't use the progress lines to indicate what work is done and what work
> needs to be completed. I use it as an indication of generally where we
> are
> on a schedule. I have a lot of customer's who don't know how to read a
> project schedule, but because of the work and coordination (as managers of
> a
> design process) we need to have one.
>
> so.... this progress line helps my customer to quickly identify on our
> project schedule were we are.
>
> still searching for an answer.
>
> "Rod Gill" wrote:
>
>> My best practices suggest to never ever use progress lines. Better to
>> update
>> actual start and finish dates and rely on baseline data to show where you
>> should have been using the Tracking Gantt chart.
>>
>> Progress lines cause problems, because you have incomplete work in the
>> past
>> and completed work in the future. How do you determine what your
>> project's
>> resource needs are for the next few weeks?
>>
>> By updating as recommended above, all work for next week needs to be done
>> and all work for last week is complete (provided you have also moved all
>> incomplete work out to next week after updating your schedule).
>>
>> Good luck!
>>
>> --
>>
>> Rod Gill
>> Microsoft MVP for Project - http://www.project-systems.co.nz
>>
>> Author of the only book on Project VBA, see:
>> http://www.projectvbabook.com
>>
>>
>>
>>
>> "Project Manager" <ProjectManager(a)discussions.microsoft.com> wrote in
>> message news:291804E1-5D0D-4879-8D3C-8C29DE5586D6(a)microsoft.com...
>> > I'm getting a zig zag at the top of my progress line even though it is
>> > set
>> > to
>> > show the current date. It is starting the progress line at the original
>> > proejct date and then zig zagging the line to the current date. How do
>> > i
>> > fix
>> > this?
>> >
>> > __________ Information from ESET Smart Security, version of virus
>> > signature database 4978 (20100326) __________
>> >
>> > The message was checked by ESET Smart Security.
>> >
>> > http://www.eset.com
>> >
>> >
>> >
>>
>> __________ Information from ESET Smart Security, version of virus
>> signature database 4978 (20100326) __________
>>
>> The message was checked by ESET Smart Security.
>>
>> http://www.eset.com
>>
>>
>>
>> .
>>


 |  Next  |  Last
Pages: 1 2
Prev: importing schedule into outlook calendar
Next: Microsoft Office has identified a potential security concern