Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

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.

Disable de Sirens -- But Put Out de Critical Path Fires, Too!

No replies
Stephen Devaux
User offline. Last seen 22 weeks 5 days ago. Offline
Joined: 23 Mar 2005
Posts: 665

I just posted a new article “Disable de Sirens – But Put Out de Critical Path Fires, Too!” on my blog. This article is in explanation to some readers who felt that some of my comments in my previous article (“Whaddya Do When the Critical Path Changes?” ) represented an overreaction to the critical path changing.

As the new article says, my reaction was somewhat hyperbolic (a result perhaps of my Bajan heritage). But I also recognized that I needed to explain in greater detail how a critical path migration should always trigger specific new analysis and perhaps a new plan. This article provides that explanation, while also showing that the negative impact analyzed in the previous article would likely go unrecognized and unaddressed due to limitations in (1) current PM techniques and (2) most current project management software packages.

Fraternally in project management,

Steve the Bajan