Task Not Marked AS Completed

[Raja]

Hi,

I've a particular task that has a duration of 3d. The task is of type fixed
duration. The task has two resources assigned to it. also the task is a
predecessor to another task. Now the resources booked time for two days and
both the resources made the remaining work as zero after booking time for two
days. But in the project plan the precentage complete of the task is shown as
only 67 % but actually the remaining work is zero. How could i solve this
problem ? is there any calculation setting i have to do?

 

[German Popken]

%complete shows the quotient of the actual duration (2d) by the planned
duration (3d) = 67%

if you want the task to be fully completed (with the blue marker in
front...) just enter 100% for % complete


Raja schreef:

 

[Jeanders]

I believe that if in this scenario you enter 100% in the "% Complete" column
then the "actual duration" will increase from 2 days to 3 days and the
"actual finish date" will be populated with "finish date". This will
represent that the task took a day longer than it actually took and may show
an incorrect start date for the preceeding tasks.

To avoid this I would enter the true 'Actual Finish Date' and it will mark
the task as 100% complete and keep your schedule calculations accurate.

%complete shows the quotient of the actual duration (2d) by the planned
duration (3d) = 67%

if you want the task to be fully completed (with the blue marker in
front...) just enter 100% for % complete


Raja schreef:

 

[JulieS]

Hi Raja,

Just an added note. As German Popken noted, the reason why the task is not
100% complete is because there is still 1 day of remaining duration on the
task.

Instead of setting the % Complete to 100%, I suggest setting the remaining
duration to 0. If you set the task to 100% complete (duration measurement),
the actual duration will remain at 3 days and show a trailing split at the
end of the task. The resources finished their work on day two, but the task
did not finish (Actual Finish) until the end of day 3.

I hope this helps. Let us know how you get along.

Julie

Visit http://project.mvps.org/ for the FAQs and additional information about
Microsoft Project

%complete shows the quotient of the actual duration (2d) by the planned
duration (3d) = 67%

if you want the task to be fully completed (with the blue marker in
front...) just enter 100% for % complete


Raja schreef:

 

[Jan De Messemaeker]

Hi,

People should think better before using fixed duration.
It means that statements about work CAN NOT change duration.
Both resources declare their work finished in 2 days, but you, the plklan
owner, told Project that it should disregard this,, that duration would be 3
days whatever.

All of these problems an suggestions to heal the fact that you tell Project
theduration should be fixed, but yoy don't accept the fact that Project does
that for you)

HTH

--
Jan De Messemaeker, Microsoft Project Most Valuable Professional
http://users.online.be/prom-ade/
For FAQs: http://www.mvps.org/project/faqs.htm

Hi Raja,

Just an added note. As German Popken noted, the reason why the task is not
100% complete is because there is still 1 day of remaining duration on the
task.

Instead of setting the % Complete to 100%, I suggest setting the remaining
duration to 0. If you set the task to 100% complete (duration measurement),
the actual duration will remain at 3 days and show a trailing split at the
end of the task. The resources finished their work on day two, but the task
did not finish (Actual Finish) until the end of day 3.

I hope this helps. Let us know how you get along.

Julie

Visit http://project.mvps.org/ for the FAQs and additional information about
Microsoft Project

 

[German Popken]

I have the same behaviour of remaining duration and I only use "fixed
units" tasks.


Jan De Messemaeker schreef:

Hi,

People should think better before using fixed duration.
It means that statements about work CAN NOT change duration.
Both resources declare their work finished in 2 days, but you, the plklan
owner, told Project that it should disregard this,, that duration would be 3
days whatever.

All of these problems an suggestions to heal the fact that you tell Project
theduration should be fixed, but yoy don't accept the fact that Project does
that for you)

HTH

 

[Jan De Messemaeker]

Hi German,

Well then you forced Project into that end date in a different way (Finish
no earlier than, or Must finish on). Without constraints, when both
resources declare remaining work 0 the duration becomes 2 days.
In other word, this behavior only happens when you ask Project explicitly to
do it that way.
HTH

 

[German Popken]

Jan, quite right,

however, I was meaning to refer to the %complete and not to MSP's
behaviour of durations...

maybe you can clarify the following situation for me:

task start: 1-6-06
task finish: 1-9-06
fixed units, effort driven
no constraints
one resource 100%

when entering remaining work = 0,
- %work complete changes to 100% and
- the duration changes like you said (finish date changes to the date
when the
resource last entered some actuals)

so far, so good, but...

- %complete stays at 36%, I have to manually change it to 100%


....to me this is quite annoying,
what can I do to automaticly have %complete change to 100%?


GP


Jan De Messemaeker schreef:

 

[Jan De Messemaeker]

Hi,

I've never seen this (for me %complete indeed becomes 100)
Could it be Tools, options, Calculation,
"Updating Task Status updates Resource Status"?
When I uncheck that I get this schizophrenic behaviour.
So chck it to see.
HTH

 

[German Popken]

works fine...thX

Jan De Messemaeker schreef:

Hi,

I've never seen this (for me %complete indeed becomes 100)
Could it be Tools, options, Calculation,
"Updating Task Status updates Resource Status"?
When I uncheck that I get this schizophrenic behaviour.
So chck it to see.
HTH

 

[Steve House]

Do you by chance have the switch in options "updating task status updates
resource status" turned off? If it's on, the default, updating % complete
also updates % work complete and vice versa. IF it's off, the link between
the two metrics is severed and each must be entered independently.

 

[Steve House]

LOL - sorry, I answered before I saw you already had. My bad.

 

[German Popken]

thX anyway...

Steve House schreef:

LOL - sorry, I answered before I saw you already had. My bad.
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit http://www.mvps.org/project/faqs.htm for the FAQs

Hi German,

Well then you forced Project into that end date in a different way (Finish
no earlier than, or Must finish on). Without constraints, when both
resources declare remaining work 0 the duration becomes 2 days.
In other word, this behavior only happens when you ask Project explicitly
to
do it that way.
HTH