Slowly catching up after a very busy week with PC Expo in Melbourne as the highlight.
I was honoured to be asked to perform the official welcome on behalf of the Chartered Institute of Building (CIOB) at the start of the two-day event. This year CIOB is celebrating its 190th anniversary and continues its support for professionalising the construction industry. For more on CIOB Read the opening PPT: https://mosaicprojects.com.au/PDF-Gen/Expo-AUS-2024_CIOB.pdf
During the event Iwas supporting both the CIOB and PGCS in the exhibition area.
- See more on the CIOB: https://www.ciob.org/
- See more on PGCS: https://consec.eventsair.com/pgcs2025
But, my major focus was my Masterclass presentation Assessing Delays in Agile & Distributed Projects, you can download the presentation and see more on forensic delay analysis at: https://mosaicprojects.com.au/PMKI-ITC-020.php#ADD
Thanks Pat.
CPM oversimplifies, and this has always presented limitations for project management purposes. In particular, CPM has always struggled to represent resource constraints adequately. It also represents all relationships between successive tasks as governed by "hard" logic, when only a minority of relationships are really "hard".
For forensic delay analysis, however, the critical path as a concept still remains necessary to deconflate the competing causes of delay on any given time interval. That is to say, any task NOT on the critical path is deemed NOT to be causative of delay during an interval, on the grounds that non-critical tasks fail the but-for test.
As a deconflater of competing causes of delay over an interval, the critical path does not have any conceptual competition. For this reason, I don't think that, when it comes to forensic delay analysis, that it is going to become redundant any time soon!