Actual Work entry behavior

[Scott McClure]

We enter actuals for generic resources using the Task
Usage view. When Project believes we've entered more
than available for a given resource for a day, it takes
it upon itself to move some of the time into the future.
Since this is actual time this is not correct. There are
any number of reasons we have gone over. If the time is
then removed and re-entered, Project leaves it alone. Is
there any way to turn this behavior off?

TIA,
Scott

 

[Gary Chefetz [MVP]]

Scott:

Typically this behavior is driven by task type. When you enter work against
a fixed-duration task, project will attempt to distribute this across the
duration. You might want to enter hours beyond your standard calendar as
overtime work.

--
Gary Chefetz [MVP]
http://www.msprojectexperts.com

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.

 

[Scott McClure]

Our tasks are fixed units. The resources are generic and
the possibility of "overtime" depends on many factors,
most of which can't currently be predicted. Likewise,
the person entering the time doesn't know when or if the
amount of time entered is "overtime." It could be real
overtime or just some "extra" resource being given some
of the work (even people moved from shop to shop). In
short, entering actual overtime is completely impractical.

So, the original question remains -- is there any way to
turn this off (for fixed unit, effort driven tasks)?

Thanks

 

[Scott McClure]

Again, this implies that I know what time was overtime
prior to entry and/or plan the overtime by task. In
fact, it may not even be overtime but just adding
resources to a project without formally increasing the
number of people available for that task/project. This
will not work in our environment. Unless we reenter the
time to force Project to accept, the Actual reported
times are just flat wrong!

I don't suppose there's any way to make MSPS put the
extra time into overtime rather than into days in the
future.