Re: Actual Work vs. Work vs. Duration
- From: ahelp <ahelp@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 5 Sep 2007 15:02:04 -0700
Hi Ron,
To keep your actual work from jumping to the estimated work when the task is
complete, reduce remaining work to zero rather than marking it 100% complete.
When you mark a task 100% Complete, Project assumes the initial start and
finish dates as well as estimated work. The most granular way to update a
task is through Tools -> Tracking -> Update Tasks...
--
Mike
"Dave" wrote:
Firstly you should create your plan. Duration and work are not the same.
in Project. So, in order to estimate the work required to complete each
task, you should enter this in the work column (you do not say if you
are using a plan with resources assigned to tasks so I shall assume that
you are not).
The duration should measure the period over which that work is spread.
So your 12 hours of work could have a duration of a week, or 1.5 days
depending on how intensively or exclusively somebody works on it.
Once you have completed your plan, you should baseline it. This will
preserve a copy of the planned work and planned start/stop dates.
Tools/tracking/save baseline for this.
You don't say what view/columns you are using to mark the work 100%
complete, but after having set a task as complete, you can change the
work on it to represent the actual work. The original estimate is of
course saved in the baseline. Alternatively, set the work to be the
actual work before marking it 100% complete.
If you say whether or not you have resources in your plan and what
columns/views you are working with, we can give more precise help.
Hope this helps.
Dave
Ron West wrote:
I am relatively new to MS Project and I am working on a complicated
plan in which I would like to do the following:
1. Estimate out x numbers of hours for a bunch of tasks
2. Record the actual number of hours it took to complete the tasks
(without affecting the original estimate)
3. Mark a task as complete even if the actual hours were less then
estimated (again without affecting the original estimate)
I think that this would seem simple. I have done the following:
1. Used "duration" to track estimated hours (probably not correct but
I can't see where this would be better placed)
2. Used "actual work" to track actual hours
Problem is that when I make a tasks duration say 12 hours and it only
takes 8 (I put this value in Actual Work), and then I mark it complete
(%Complete) the value for Actual Work is converted to 12.
Any help would be greatly appreciated.
- Follow-Ups:
- Re: Actual Work vs. Work vs. Duration
- From: Ron West
- Re: Actual Work vs. Work vs. Duration
- References:
- Actual Work vs. Work vs. Duration
- From: Ron West
- Re: Actual Work vs. Work vs. Duration
- From: Dave
- Actual Work vs. Work vs. Duration
- Prev by Date: Re: Adding weeks to my project in MSP 2003
- Next by Date: Re: Why are some of my cell backgrounds blue in Project 2007?
- Previous by thread: Re: Actual Work vs. Work vs. Duration
- Next by thread: Re: Actual Work vs. Work vs. Duration
- Index(es):
Relevant Pages
|