Dates are looking strange after applying actual time against tasks

[Robin Rice]

Hello-

We have tasks that are fixed-work, effort-driven. For just a FEW of these
tasks, after we have the resources enter hours in PWA, the dates in MS
Project push out by MONTHS and the resource allocation shrinks to a very
small percentage.

An example: A task was planned and baselined at 12 hours for one resource
at 30% allocation. The person entered 14 hours to the task over one week and
"0" remaining work. NOW the schedule in MS Project shows 2 things: It
reduced the resource allocation to 1% and stretched the end date out 6 months!

Another example: A task was planned for 3 hours in Feb 2006. It had 3
actual hours entered against it in February in PWA. However, the MS Project
schedule shows the task STARTING in 1984 and FINISHING in 2049.

This stuff is NOT occuring with every task (or else we'd be jumping off a
cliff). There are just a few things that are getting very strange results.

Any ideas out there??

Thanks
Robin

 

[Gary L. Chefetz [MVP]]

Robin:

This type of behavior generally indicates bad data, but there's not much
more anyone can say without a lot more specific information and perhaps even
hands on the plans.