LOL - No offense, but I don't know what to think because honestly I can't
figure out what you're really doing or why you're doing it.
The way I go about it is - this task is to build 100 widgets. I know how
Fred usually manages to build 10 a day when he's not otherwise distracted.
So working 100% it will take him 10 days (duration) to build 100. Fred
works 8 hours per day. I assign him 100% to the task. Thus it will require
80 man-hours to build 100 widgets. Fred gets paid $20/hr. Thus my project
budget is $1600 to build the required 100 widgets.
The inputs in Project are: Fred works 8-5 with an hour for lunch, M-F.
Fred's pay rate is $20/hr. Fred doesn't need to be doing anything else at
the same time so I can use him 100%. And working full time I expect the
task to take him 10 days to complete. I put in the duration estimate and
assign Fred to the task. Project calculates it is an 80 man-hour task and
will cost $1600. Project looks at Fred's resource calendars to see what
days and hours Fred going to be there to work on the widgets and uses that
info to compute when the task will start and when the 100 widgets will be
completed. In other words, it requires 80 hours of work and Fred's calendar
says when those 80 hours will take place - like Friday counts for 8 hours of
duration because Fred is working but Saturday doesn't count for duration
because it's Fred's day off.
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs