Re: Work vs Actual Work
- From: JanoV <JanoV@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 13 Nov 2007 08:31:00 -0800
Hi John,
thanks for your answer.
My question is stupid simple - how to correctly complete task
(%Completed=100%) without losing information about entered actual work, that
should be different from Work. I didn't find any usefull information in help,
nor in discussion.
But I agree with you - using MSP is big mistake ... Implemented logic of
calculation is incomprehensible for most of users. And real support doesn't
exist.
Thanks for your time.
JanoV
„John" napísal (napísala):
In article <F3C24950-AFCB-4961-82FF-6FC888FED7BD@xxxxxxxxxxxxx>,.
JanoV <JanoV@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi Joe,
you're right. Update the "Remaining Work" field to zero after updating
"Actual Work" field to .25 hrs will mark task 100% (%Completed).
But the problem is this:
- field "Work" is also updated to .25 (Work=Actual Work) - not so big
problem, original planned Work should be stored in baseline
- field "Duration" (and Finish Date) is recalculated - and this is big
problem - all successors can be automatically recalculated and this totally
change project plan.
Is there any way how to complete task without recalculation of many fields?
Thanks
Jan
Jan,
I think you're missing the point of having a dynamic schedule. Tasks
rarely start or finish on the original planned dates. That's life. As
tasks are completed early or late, the dependent tasks should shift in
time accordingly.
There may be some cases where dependent tasks need a conditional link.
For example, a particular process can't start in the middle of the day
but it also cannot start until a previous task is completed. In that
case an appropriate schedule structure must be set up to support both
requirements. Or in another case, a fixed amount of time is available
during which a task can be completed but the task work effort is not
full time. In that case a fixed duration type task might be appropriate.
If for some reason you do not want your schedule to be recalculated
based on progress, then you should examine your schedule logic and/or
not use Project at all.
John
Project MVP
„Joe" napÃsal (napÃsala):
What Julie is trying to say is to update the "Remaining Work" field to zero
after you put the .25 hrs. in the Actual Work field. This will mark the
task
100%.
"GreenMonster" wrote:
no matter what I do the "Actual Work" field always populates with the
same
value that it's the "Work" field when I change the %Complete to 100.
If I put .25h in "Actual Work" and chage "Work" to 0 hrs, then put the
task
at 100% complete, the Actual Work value changes to 0. What am I missing?
"JulieS" wrote:
Hi GreenMonster,
Try setting the Actual Work to .25h and then enter zero for the
remaining work. When you said the task was 100% complete, Project
assumed it took all 4 hours.
I hope this helps. Let us know how you get along.
Julie
Project MVP
Visit http://project.mvps.org/ for the FAQs and additional information
about Microsoft Project
"GreenMonster" <GreenMonster@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:1AB6759C-B153-42E2-8E50-F735E7245559@xxxxxxxxxxxxxxxx
I have a task with the following info:
Duration = 1day?
Work = 4hrs
Start = 10/16/06
Finish = 10/16/06
I completed the work today (10/11/06) and it took only 15 mins. I
put
.25
hrs in the "Actual Work" column and then change the "% Complete" in
the task
info to 100%, the "Actual Work" then changes back to 4hrs instead of
.25hrs.
Why doesn't "Actual Work" retain the .25hrs that it took to complete
the task?
- Follow-Ups:
- Re: Work vs Actual Work
- From: John
- Re: Work vs Actual Work
- References:
- Re: Work vs Actual Work
- From: JanoV
- Re: Work vs Actual Work
- From: John
- Re: Work vs Actual Work
- Prev by Date: Re: Work vs Actual Work
- Next by Date: Re: Baseline change problems
- Previous by thread: Re: Work vs Actual Work
- Next by thread: Re: Work vs Actual Work
- Index(es):
Relevant Pages
|