Re: Tracking Project Updating Time
- From: "Rod Gill" <rod AT project-systems DOT co DOT nz>
- Date: Sat, 16 Dec 2006 13:24:41 +1300
First you lose most of the value when you track this way. Much, much, better
to update the individual tasks. If your time*** system does not read
current tasks from Project then change the time *** system or stop
including the data in your schedules. Apart from actual costs, the main
benefit of accurate task updating is to predict-measure-learn from
predicting Work for each task. Updating a single task like you has little
value in my book, so why bother?
--
Rod Gill
Project MVP
NEW!! Project VBA Book, for details visit: http://www.projectvbabook.com
"Kilen" <Kilen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4A20F673-5323-4F4F-9269-1BF99D674B00@xxxxxxxxxxxxxxxx
Hi!
We've started keeping track of time spent in updating the project, and
have
included this as an unlinked task in each project. Some PMs are calling
in
Project Admin or Project Updating. What I am seeing, though, is that they
are setting the duration to last the length of the project. In doing
this,
it isn't showing the properly critical path. Can you suggest a better way
of
keeping track of this data? Would it maybe be better for them to only
have a
one week duration on the task, but keep adding the hours that they need
to?
This task is more of a log than anything.
I hope that I am making sense in describing my scenerio. Any thoughts
would
be appreciated!
.
- Prev by Date: Re: Printing a Publisher booklet
- Next by Date: Re: Isn't there a "Machine" Resource Type???
- Previous by thread: Re: Printing a Publisher booklet
- Next by thread: Re: Tracking Project Updating Time
- Index(es):
