View Single Post
  #24   Spotlight this post!  
Unread 18-12-2007, 15:28
Tom Bottiglieri Tom Bottiglieri is offline
Registered User
FRC #0254 (The Cheesy Poofs)
Team Role: Engineer
 
Join Date: Jan 2004
Rookie Year: 2003
Location: San Francisco, CA
Posts: 3,188
Tom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond repute
Re: Project Management and FIRST?

Quote:
Originally Posted by Alan Anderson View Post
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.
Of course. As Alan said, never publish that extra time per task is being given. Just schedule deadlines with this fact in the back of your mind. Obviously, the bigger the component, the longer it will take, and the more importance it holds to the overall completion of the project.
Reply With Quote