K
Kathy S
We are using MSP Pro 2003 SP2 with Project Server 2003 with SP2a using
Non-managed time periods. A task is created using Fixed Duration, not
Effort Driven, starts 8/21/06 with 5d duration which ends 8/25/06, no
predecessors. One resource is assigned, therefore, the resource is
defaulted to 100% Units for 40 work hours. So far all is well. The
resource adds 1 hr actual work in PWA on 8/21/06; the project managers
updates the time in PWA. In MSP, the resource's Units now reflect 488%
(work=40; actual work=1; remaining work=39). In MSP's Resource Usage
view, the resource's work hours for this task for the week of
8/21-25/06 shows 1-0-0-0-39. (39 hr divided by 8 hr/day = 488%) The
real question becomes...Why did MSP place the remaining work hours (39)
on the last day of the task instead of spreading the remaining 39 hours
over the remainder 4 days. This happens on many tasks in many
projects.
Thanks,
Kathy
Non-managed time periods. A task is created using Fixed Duration, not
Effort Driven, starts 8/21/06 with 5d duration which ends 8/25/06, no
predecessors. One resource is assigned, therefore, the resource is
defaulted to 100% Units for 40 work hours. So far all is well. The
resource adds 1 hr actual work in PWA on 8/21/06; the project managers
updates the time in PWA. In MSP, the resource's Units now reflect 488%
(work=40; actual work=1; remaining work=39). In MSP's Resource Usage
view, the resource's work hours for this task for the week of
8/21-25/06 shows 1-0-0-0-39. (39 hr divided by 8 hr/day = 488%) The
real question becomes...Why did MSP place the remaining work hours (39)
on the last day of the task instead of spreading the remaining 39 hours
over the remainder 4 days. This happens on many tasks in many
projects.
Thanks,
Kathy