It all depends on what one is planning and the degree of understanding the job being planned. I have worked on plans where everybody was quite clear what needed to done and the interdependencies between each player. One can easily generate a robust logically driven network with time and resource in less than a month.
On the other hand I have worked on large systems engineering projects where one of the key roles of the planner was to drive out engineering process (in conjunction with the Chief Engineers) in addition to duration and resource. In such cases the engineering process to be followed defines the planning dependencies. Naturally this type of project takes much longer to reach a satisfactory programme that all players buy in to. It has taken me around 5 to 8 weeks to have a rough programme that all buy into and then another couple of months to polish. Activity size was around 1,300 to 2,000 activites with an appropriate amount of dependencies.
Are you going to type one by one of the 2000 activities?
Are you going to input dependencies one by one activity?
Do you have an orderly procedure that takes you through the whole scope that helps you define the division of stretches, project elements and activity operations (actions)to in turn define activities? And whether you are going to define activities that will eencompass one trade or crew, or will they encompass more than one?
In summary, do you have a defined set of proven procedures, guidelines and criteria the take you through the process of designing schedules?
Project nature is big factor that defines schedule development duration. But, I would say that schedule development nature is a bigger one. Especially when we are talking about thousands of activities.
In other words, how long does it take to go from Cancun, Mexico to Paris, France?
That depends in large part upon the type of schedule being defined and the caliber of the resources the planner has to draw upon. Scheduling work that is repetitive in nature (such as equipment maintenance or construction) where the scope has a large overlap with historical projects should be fairly quick to produce.
Projects that encompass something entirely new (list software development, design, etc.) would require more effort in defining the tasks. Im not sure that a metric for scope development is applicable when the project is completely unknown (has to be defined from scratch).
RE: how long should we take to produce program
It all depends on what one is planning and the degree of understanding the job being planned. I have worked on plans where everybody was quite clear what needed to done and the interdependencies between each player. One can easily generate a robust logically driven network with time and resource in less than a month.
On the other hand I have worked on large systems engineering projects where one of the key roles of the planner was to drive out engineering process (in conjunction with the Chief Engineers) in addition to duration and resource. In such cases the engineering process to be followed defines the planning dependencies. Naturally this type of project takes much longer to reach a satisfactory programme that all players buy in to. It has taken me around 5 to 8 weeks to have a rough programme that all buy into and then another couple of months to polish. Activity size was around 1,300 to 2,000 activites with an appropriate amount of dependencies.
Hope this helps
RE: RE: how long should we take to produce program
Bryce:
Are you going to type one by one of the 2000 activities?
Are you going to input dependencies one by one activity?
Do you have an orderly procedure that takes you through the whole scope that helps you define the division of stretches, project elements and activity operations (actions)to in turn define activities? And whether you are going to define activities that will eencompass one trade or crew, or will they encompass more than one?
In summary, do you have a defined set of proven procedures, guidelines and criteria the take you through the process of designing schedules?
Project nature is big factor that defines schedule development duration. But, I would say that schedule development nature is a bigger one. Especially when we are talking about thousands of activities.
In other words, how long does it take to go from Cancun, Mexico to Paris, France?
Tomas Rivera
RE: how long should we take to produce programmes?
That depends in large part upon the type of schedule being defined and the caliber of the resources the planner has to draw upon. Scheduling work that is repetitive in nature (such as equipment maintenance or construction) where the scope has a large overlap with historical projects should be fairly quick to produce.
Projects that encompass something entirely new (list software development, design, etc.) would require more effort in defining the tasks. Im not sure that a metric for scope development is applicable when the project is completely unknown (has to be defined from scratch).
Bernard Ertl
<a href="http://www.interplansystems.com/">InterPlan Systems Inc. - Project Management Software, Project Planning Software</a>