CPM Schedules have limited use in horizontally distributed projects!

Member for

21 years 8 months

The focus on my postings is on the statement:

CPM Schedules have limited use in horizontally distributed projects!

A statement I do not agree with.

CPM not limited to logic and date constraints but that can also handle resource constraints, financial constraints, consumable resources and spatial resources among others is of much use in horizontally distributed projects. On the other hand it might be argued that scheduling software that is poor at handling these other constraints do have limited use in horizontally distributed projects.

In my area of work jobs before startup usually do have a well defined scope of work and most have some horizontally distributed activities. I never had a need for the so called Agile Methodology.

Member for

24 years 9 months

The focus of the presentation and post is the fact there are a lot of projects where CPM has no value to add, starting with projects that use the Agile methodology.  BUT in many cases hard dollar, fixed time contracts still need EOTs and other normal contract managment capabilties.   Try downloading the presentation from: https://mosaicprojects.com.au/PMKI-SCH-010.php#Issues-A+D

Member for

21 years 8 months

Same as for traditional renewable resources resource leveling for financial constraints shall look for optimal or near optimal solution.

Same as for traditional renewable resources resource leveling for spatial resources shall look for optimal or near optimal solution. Using hard links to solve financial resources is not a good idea, manual resource leveling is not a good idea.

Member for

20 years 5 months

Patrick, wouldn't a business optimise cash flow?

Member for

21 years 8 months

I see no big problem with assessing delays in horizontally distributed projects; I see problems with the current practice promoted by our courts and the the AACEI that still insist on playing the float game. That AACEI practice is useless does not mean scheduling is useless.

I agree with the statement that the primary consideration in planning and managing a distributed project is optimising resource flows.