Website Upgrade Incoming - we're working on a new look (and speed!) standby while we deliver the project

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Delay due to preparatory activities.

5 replies [Last post]
vinod raturi
User offline. Last seen 7 years 30 weeks ago. Offline
Joined: 14 Aug 2006
Posts: 57
Hi all ,

My query is how do you deal with preparatory activity in MS project .
For eg ,In our co. most of the people knows that to set up 1/2 inch nozzle will take 1/2 hour ,( an activity which is reflected in barcharts ) but still it is found that it is never on time , main culprit being time required for gathering resources , for fitting. OR you can say we dont have data on time required for preparatory activity.

What do you guys do in such cases. ?

How do you reflect such delays in MS Project ?

Do you guys take some percentage of time for prep activity ?

I need all inputs from gurus out there .

regards,

Replies

vinod raturi
User offline. Last seen 7 years 30 weeks ago. Offline
Joined: 14 Aug 2006
Posts: 57
Hi guys ,

Do you generally calculate time for prep activity as some sort of percentage time , utilised for actual actvity.

Today i was surprised tolearn that the activity of 10 hrs duration ,which i am tracking ,required an effort of 3 persons for full 12 hours yesterday so that activity can be started today .

I guess it is time for me to keep eye on preparatory activites , and resources required for the same.
Tom Farmer
User offline. Last seen 19 years 6 weeks ago. Offline
Joined: 19 Jan 2005
Posts: 19
Groups: None
Food for thought about prepartory activities . . . if there is a resource change of hands, even within the same company, consider breaking out the acitivity. Additionally, be guided by managable activity durations. Site activities greater than 30 calendar days should be split into increments not exceeding 30 calendar days to enable identification of slippage or production deviation in time to recover.
John Lawson
User offline. Last seen 12 years 23 weeks ago. Offline
Joined: 6 Oct 2004
Posts: 113
Hi,

In cases as descibed - I usually use the activty description as "Procure & Install" and have a duration that reflects the activity.

John
James Griffiths
User offline. Last seen 16 years 41 weeks ago. Offline
Joined: 19 May 2006
Posts: 435
Groups: None
Hi Vinod,

This is always something that we encounter when describing activities. When discussing with the engineers, they always fail to think of the "preparatory" activities. As a result the activities always take longer that shown on the project.

Yes, you could insert the prep’. activities as an individual task, but it then becomes a monster to update. Personally, I try to ensure that the duration of the task takes account of the prep’. activities. This is where the individual programmer’s style is employed - in knowing the full content of the activity as opposed to just its name.

James.
Zhang Haixiang
User offline. Last seen 5 years 2 weeks ago. Offline
Joined: 14 Apr 2005
Posts: 250
Groups: None
for me this is not a problem.

task name is only a short description of a set of works.

e.g. "nozzle installation" make contains some hidden works, get the nozzle from warehouse, then goto jobsite....

any delay will cause "nozzle installtion" delay, so when update this task, show the delay that’s all.

You do not need to think in such a detail way.
But some preparation works are very important, and should be consider as task. for example pipe fabrication,equipment procurement/delivery...

HTH