Work or Duration?
When entering task estimations into MS Project, do you use work or duration?
As a reminder, work is the length of time a task will take (e.g., 8 hrs), while duration is the actual time that passes before the task is complete (e.g., 2d).
I prefer to receive work estimates rather than duration estimates from my teams, so I understand the cost of the project. If the teams provide duration, they are already considering factors outside the actual task at hand, most of which is not billable, and leaving me with no idea what the real work effort will be.
Instead, I'd rather have the teams provide me only with the work hours required to complete each task, then I as the PM can factor in overhead, productivity factors, holiday plans, etc., to arrive at a final delivery date. This simplifies the estimation process, keeps the team focused on the task at hand, lets me know the real work effort, and helps ensure that estimations are determined consistently across tasks and teams.
I usually ask for estimations in hours (the default unit of measure for work in MS Project). Then, when I enter the work effort into Project, it automatically calculates the task duration in days (the default unit). Then I can see from the plan's critical path when the project is likely to end and make any necessary adjustments.
As a reminder, work is the length of time a task will take (e.g., 8 hrs), while duration is the actual time that passes before the task is complete (e.g., 2d).
I prefer to receive work estimates rather than duration estimates from my teams, so I understand the cost of the project. If the teams provide duration, they are already considering factors outside the actual task at hand, most of which is not billable, and leaving me with no idea what the real work effort will be.
Instead, I'd rather have the teams provide me only with the work hours required to complete each task, then I as the PM can factor in overhead, productivity factors, holiday plans, etc., to arrive at a final delivery date. This simplifies the estimation process, keeps the team focused on the task at hand, lets me know the real work effort, and helps ensure that estimations are determined consistently across tasks and teams.
I usually ask for estimations in hours (the default unit of measure for work in MS Project). Then, when I enter the work effort into Project, it automatically calculates the task duration in days (the default unit). Then I can see from the plan's critical path when the project is likely to end and make any necessary adjustments.
posted by michael at 7:52 AM
3 Comments:
I liked your clear description of work effort versus duration. As a technical consultant who's often asked to provide estimates, I find myself giving durations. Just recently, however, I was asked to distinguish between actual effort versus duration, and it made my brain hurt for a bit. Your post was a bit of clarify. Thanks!
I'm not in IT, but in Biotech, and I'm wondering if there's a way to capture both work and duration. There are some tasks that take two weeks, but actual hands-on time for the resource is only 10 hours (1 hour/day). What are some ways to use the work to estimate costs, but then use duration to estimate timelines?
Thanks
I m studying this for the last 4 days. I m very confused because hours are involved in both effort n duration.... a good example from everyday life will make it clear
Post a Comment
<< Home