Welcome to Project Management Questions!

You can ask any question on Project Management and you can rest assured that real Project Managers will answer your shortly!

Is it OK to pad the project schedule?

We all know that project managers are often accused of "padding" the project schedule, and rightly so. So my question is, is it OK to pad the project schedule, and to what extent? How much padding, in percentage, should I add to the project schedule?
asked 6 years ago by anonymous

3 Answers

Rather than padding the schedule, budget, etc. you might consider using PERT.  The output of a PERT estimation is a range of time and/or dollars which has an associated confidence level.  This will help you in the event the project turns out to be more complicated or tasks always seem to be about the worst case.  

It also might be better to set aside two sets of time, funds, etc.  known as contingencies and reserves.  Contingency is for known risks which may happen and will cover them.  Reserves are used for unknown risks.  While most often used in conjunction with budgets, there is no reason the same concept couldn't be applied to time, with an appropriate explanation.  I generally look for 15-20% for contingencies and the same amount for reserves, if appropriate.
answered 6 years ago by sdcapmp (45,840 points)
I know many project managers who pad the estimates twice: when they receive the estimates from the team members/team leader, and when they create the project schedule. For example, let's say that one of the team members said that a task will take 1 day, the project manager will then make it 2 days (without even thinking twice), and then while scheduling the project, the project manager will give it 3 days, because of a 50% across the board padding on the project schedule. I think this is extremely inefficient and it will result in Parkinson's Law in complete action on the project (work expands or shrinks to fill in the time allocated for its completion), so if you allocate 3 days to a task that would normally take 1 day to complete, then the task will take the whole 3 days to complete!

Now I'm not saying you shouldn't pad the schedule, you should definitely pad it, but padding should be controlled and reasonable. When you pad your project, you should consider 3 things:

- The accuracy of the person telling you how much time a task will take: For example, some team members say that a task will take 1 day, but it really takes 4 days.

- The complexity of the task: If the task is complicated, then it's definitely better to pad it well.

- The amount of the unknowns in the task: Does the task have a lot of unknowns at the time of the scheduling? If it does, then you should substantially pad it (I would also split the task into subtasks where the unknown part is a task of its own that is not on the critical path).

Now taking the above padding into consideration (I wouldn't consider the above "padding" by the way, I would consider it better estimation), you can then pad the whole schedule by 5% to 10%.
answered 6 years ago by humblepm (17,390 points)
it depends, if there are uncertain areas or research components then it would be fine for padding, but have proper clarifications for the % of padding.
answered 6 years ago by abeetha (360 points) edited 6 years ago by humblepm

Related questions

© 2010 - 2012 Project Management Questions - All Rights Reserved