Many a times, we come across a situation wherein the task estimate has been done based on standard skillset/expertise assumption. For example, coding a function in C#.NET is estimated as 12 days.
An expert programmer in .NET may take just 8 days to complete it, whereas a beginner may take more than 15 days for the same task.
How to handle this in MS Project?
1. By entering different rates for different resources?
2. By entering task durations based on resources assigned?
3. Or do Optimistic & Pessimistic task durations take care of this variance?
Can we have some experts throw some light on this subject. Saving Changes...
When you ask "how to handle this in MS Project?" - I wasn't sure if you meant in timing or in budget or both? Very rarely do I know right off the bat who my resources shall be. However, when working with my leads to create WBS, depending on the timing and type of project, I either capture in my WBS the PERT time and\or varying degrees of time depending on resource (jr, mid, sr., etc) and then capture in the schedule later (actual time based on resource allocation) on once my resources have been assigned. Make sense? Saving Changes...
It sounds like you just want to give a more accurate picture which translates to managing expectations. I would use the longest time possible based on the information you have. At the same time, you may have to manage the impact of finishing the task early if you have a more skilled resource. An impact assessment would be best for this. Some PMs call this a positive risk. Saving Changes...
Wayne MackRetired| RetiredSouth Riding, Va, United States
First, ask yourself if this is a problem that truly needs to be solved. There is always going to be variation between estimated and actual levels of effort.
For software development, I usually lay out a timeline of the most critical tasks and ensure the better developers are working the critical path. This lets the less experienced developers to work at their own pace on the less critical areas.
Will all of your tasks finish exactly as scheduled in Project? No, but what matters is getting the overall project done on time. Do your best with estimates and manage the critical path.
Saving Changes...
Anonymous
Using the PERT Analysis feature within MS Project should get you what you are looking for.
For help on the subject search on Pert Entry Sheet in MS Project.