![]() |
|
#8
|
|||
|
|||
|
If you have a task of one day duration and assign one resource at 100%, Project calculates the work = duration * assignment units.
So, 8 hours of work for one resource at 100%. So now you decide to assign two hours of overtime. By assigning overtime project subtracts the 2 hours of overtime from the 8 hours of "regular work" equaling 6 hours. The definition of a day by default is 8 hours (set in Tools > Options, or File > Options in 2010). So there are now 6 hours of regular work and two hours of overtime. The 6 hours are now used to recalculate duration. 6/8 = .75 days Again, there is a significant difference between assigning overtime and tracking overtime. If you originally had the resource scheduled for 8 hours of work and you enter 10 hours of actual work, Project will increase the assignment units. If you enter 8 hours of Actual Work and 2 hours of overtime, the assignment units will stay at 100% without triggering an overallocation. It really does matter where you add the overtime and whether you add it to the Overtime work field or Actual Overtime Work. I hope this helps. Julie |
| Tags |
| overtime work |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Task duration between 2 fixed milestones | cettolox | Project | 3 | 01-24-2012 06:33 AM |
Task cannot stop once started, but cannot continue into non-work hours
|
sullied | Project | 3 | 12-05-2011 06:32 PM |
| Work not changing duration | benoldays | Project | 0 | 02-14-2011 08:21 PM |
| Work as percent of another task | JohnG10 | Project | 0 | 12-10-2010 07:51 AM |
| Duration changes fail to update work effort | Panteledes | Project | 6 | 05-25-2010 02:27 PM |