M
Matt Piazza, PMP
Any ideas what could be causing the following unwanted results?
We are using MSP 2003 Server and Pro. We have an administrative project for
Operational tasks. We planned a resource at 2 hours per day for 6 months.
The resource using PWA Tasks, enters 1 hour for the 1st day. The project
manager accepts the update. In Project Pro Resource Usage view, we see 1
actual hour for the first day and 2 actual hours for all future business days
for six months and that the task is 100% complete with an Actual Finish date
field with a value at the 6 month date!
We setup the task as Fixed Units with Effort Driven. We have also tried
Fixed Duration without Effort Driven and experienced similar results. We
require actual hours input on a daily basis and do not allow progress by a %
complete input.
Any ideas is appreciated. Thanks in advance.
We are using MSP 2003 Server and Pro. We have an administrative project for
Operational tasks. We planned a resource at 2 hours per day for 6 months.
The resource using PWA Tasks, enters 1 hour for the 1st day. The project
manager accepts the update. In Project Pro Resource Usage view, we see 1
actual hour for the first day and 2 actual hours for all future business days
for six months and that the task is 100% complete with an Actual Finish date
field with a value at the 6 month date!
We setup the task as Fixed Units with Effort Driven. We have also tried
Fixed Duration without Effort Driven and experienced similar results. We
require actual hours input on a daily basis and do not allow progress by a %
complete input.
Any ideas is appreciated. Thanks in advance.