RE: Percent complete not populating

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Deena Blazek (DeenaBlazek_at_discussions.microsoft.com)
Date: 01/11/05 

Date: Tue, 11 Jan 2005 10:01:04 -0800

I just tested this in an open plan in pro and if I zero out remaining work
before the actuals are logged, the percent complete never updates. If I
update 'actuals', it then completes. Can you test this out?

"Michelle" wrote:

> Hello!
> Yes, there are multiple people assigned to these tasks
> although it is no more than 3 people per task. Yes there
> were actuals logged against the task at the time it is
> zero'd out. We currently have email notifications off so I
> am not sure if they were on if they would be receiving
> emails if they were turned on. It doesn't look like there
> are any updates that are made when the project manager
> publishes new and changed assignments.
>
>
> >-----Original Message-----
> >For your first iteration task, are there multiple
> resources assigned to the
> >task? Any constraints set with the task? When you zero
> out remaining, were
> >there actually 'actuals' logged to the task? Is the/Are
> the resource(s)
> >still receiving email notifies for the first iteration
> task?
> >
> >"Michelle" wrote:
> >
> >> Thanks for your reply. There are situations in which
> the
> >> PM needs to zero out the remaining work to support a
> >> particular development methodology that works in
> >> iterations. If a task isn't completed in a certain
> >> iteration the original task is zero'd out and then a
> new
> >> task in the new iteration is added with the remaining
> work
> >> added to the work. The way I understand project to work
> >> when remaining equals zero the task should be marked
> 100%,
> >> correct? Professional isn't doing this though. The PM
> >> has to mark the task 100% after putting the remaining
> work
> >> to zero.
> >> Any thoughts?
> >>
> >>
> >> >-----Original Message-----
> >> >The PM shouldn't have to zero out remaining work in
> Pro.
> >> If you open the
> >> >Plan in Pro and insert the column Actual Work
> Protected,
> >> you can see the data
> >> >that is 'transferred' from the users entering time in
> >> PWA. In time***
> >> >view, they should be entering their actual work each
> day
> >> for a given task.
> >> >Have you looked at the resources assigned to the
> task's
> >> timesheets to
> >> >validate they're entering actuals and remaining work
> is
> >> adjusted accodingly?
> >> >That is pertinent data that is exchanged between PWA
> and
> >> Pro. Another thing
> >> >to look at is if you have automatic resource leveling
> >> turned on/off.
> >> >
> >> >"Michelle" wrote:
> >> >
> >> >> I have a project manager whom after receiving
> updates
> >> from
> >> >> PWA wants to put the remaining work for a task to
> >> zero.
> >> >> The problem that is occuring is that after he zero's
> >> out
> >> >> this remaining work the percent complete is not
> >> changing
> >> >> to 100%. Does anyone have any ideas as to why this
> is
> >> >> doing this? Is he missing a step that will
> >> automatically
> >> >> mark this task as 100%?
> >> >>
> >> >> Also as part of the team's weekly status meeting
> they
> >> >> review the updates to the plan and then assign any
> new
> >> >> tasks that have been added to a certain week. After
> >> the
> >> >> task assignments are completed the project manager
> >> saves
> >> >> the plan and publishes. The team then reviews all
> >> >> assignments for the next week in the resource
> >> assignment
> >> >> view in PWA. The problem is that after the PM
> >> publishes
> >> >> the assignments the resources and the project
> manager
> >> then
> >> >> only see a portion of the assignments in the
> resource
> >> >> assignment view in PWA. Any idea why this is doing
> >> this?
> >> >>
> >> >> Thanks!
> >> >> Michelle
> >> >>
> >> >>
> >> >.
> >> >
> >>
> >.
> >
>

Quantcast