View Single Post
  #23   Spotlight this post!  
Unread 18-12-2007, 14:14
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,113
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Project Management and FIRST?

Quote:
Originally Posted by Tom Bottiglieri View Post
2) "Fluff" time - Always Always Always allow yourself a bit more time than what you initially expected. If you think manufacturing will take 2 weeks, allow yourself 2 weeks and 2 days. There are ALWAYS unforeseen problems that pop up.
If you explicitly pad the schedule and expect it to take 2 weeks and 2 days, it'll expand again and take 2 weeks and a half. Dealing with this apparent law of nature is difficult. Try fooling the schedule gremlin and officially allot only the original 2 weeks, while not starting anything else that depends on its being done until a couple of days afterward.

This represents the "fluff" as unscheduled time, so it looks bad from an efficiency point of view, but I think it's better than giving in to the urge to put running late on a task into the original schedule.
Reply With Quote