Project Management

Been There, Done That

From the Game Theory in Management Blog
by
Modelling Business Decisions and their Consequences

About this Blog

RSS

Recent Posts

George Jetson, Bring Me A Rock!

How To Obstruct A PMO

Rage, Rage Against The Dying Of The Project

Think You Have A Culture Problem? Think Again.

Finally! A GAAP Concept PMs Can Get Behind!

Categories

Game Theory, PMO, Politics, Risk Management, Strategic Management

Date

linkedin twitter facebook Request to reuse this  


There’s a very irksome characteristic of the management sciences that involves the re-introduction of established ideas, but with new names. Of course, if those ideas were all that in the first place, they wouldn’t need to be re-packaged and sold to the same people who had either tried them and found them wanting, or else rejected them out of hand in the first place.

Two examples pop to mind. In 1997, Eliyahu Goldratt published The Critical Chain, a novel about a business school professor who presents as a new and insightful tactic the idea that resources assigned to non-critical activities in a Critical Path Methodology (CPM) network can be temporarily re-assigned to the critical ones, and help shorten those activities, thereby compressing the project’s overall duration. Clever, no? The problem is, it’s an old and familiar tactic, better known by pre-1997 practitioners as “crashing the schedule.” It’s not even that novel a tactic. Anyone familiar with Critical Path Methodology would probably recommend it the first time their project’s end-date needed to be moved up.

There are other problems with critical chain (such as the added costs of assigning non-expert personnel to activities that just happened to be on the critical path), but that didn’t stop the novel’s protagonist from winning out in the end (wouldn’t you just know it?). But “critical chain” sounds so much cooler than “crash the schedule,” doesn’t it? “Crashing the schedule” is how those old guys, staring into their slow-phosphor-burning terminals and mumbling about the proper number of start-to-start relationships in the network would put it. “Critical chain” is how young, thin, hip students of young, thin, hip professors would articulate the concept.

It is, however, the same idea, with the same issues as before.

Another example is the “Life Cycle Costing” craze that hit in the 1980s. All of a sudden, estimators and cost baseline creators were being admonished to consider all of the costs a given project would incur, including post-delivery to the customer. The main example I remember from the trade magazines at the time had to do with buildings, and how important it was to take into account their predicted life-cycle energy costs and water consumption over theirs planned existence. The Life Cycle Costing push had the same two problems that critical chain had: the ideas were hardly new, and they were plagued with problems.

First off, the idea that a construction company would fail to take into account the heating and cooling costs of a building prior to selecting its design and materials is just plain goofy, if for no other reason than the accountants would want to know the basis for amortizing its depreciation. Of course the projected future costs of the projects were taken into account – otherwise it would have been impossible in almost all cases to procure funding.

Secondly, it’s really quite impossible to quantify the future of anything, and that includes the end-result of projects. Referring back to our sample building, other than commodities speculators, who believes that energy costs can be accurately priced going in to the future? And, if our building is in California, who would have believed back in, say, 1997, that water prices would spike eighteen years later, and usage controlled by the government? And those are relatively mild fluctuations compared to the chances of the building being consumed by wildfires, or earthquakes. The assertion that a given building’s “life cycle” can be accurately quantified should be considered as sound as the claims of a tarot card reader, who makes similar statements on the predicting of their customers’ “life cycle.”

Which brings us back to April’s theme, sustainability/green project management. When, in the history of business, has completing a project with an excess of wasted resources been considered a good idea? The answer is never. For example, the plastics industry was furthered from an abundance of the compounds left over from the petroleum cracking process. In economic terms, the very existence of leftover resources that even might have an economic use in a different venue is an automatic signal of a missed opportunity.

Don’t get me wrong – “sustainable” or “green” PM is a great idea, but it’s hardly new. I guess the re-branding of long-established concepts is what we have to do to stay young, thin, and hip.


Posted on: April 26, 2015 10:54 PM | Permalink

Comments (4)

Please login or join to subscribe to this item
avatar
Rachit Khanna Chief Engineer| Dastur Kolkata, West Bengal, India
So you mean that Life Cycle Costing has no meaning in today's world?


avatar
Jacob Hildebrand Program Manager| Trimble Lafayette, Co, United States
Re-branding things tends to only hide past issues that may have been present. Like the author said, it can mask old problems with spiffy new nomenclature. However, on the topic of life cycle costing; of course we can't accurately predict the future but what is important is that we try to account for future costs and scenarios, as best possible. This back-feeds into decision-making during the present and can also provide risk analysis guidance. It's a closed-loop system: by attempting to define future costs we can refine our risk analysis and when we refine our risk-analysis we can better understand future scenarios. Indeed, life cycle costing is important, even critical, but it needs to be estimated within the sphere of our influence. We can't control everything, but we can come up with contingencies!

avatar
Bernard Gore Portfolio, Programme & Project Professional| NZ Police Wellington, New Zealand
I have to disagree somewhat with Jacob. Yes, the re-branding may often be to mask issues, but this may be done for good genuine reasons - because those old issues were specific to their time, and re-branding avoids them being used to stop the re-introduction of an idea that failed previously because conditions were not right, but whose time has come!

avatar
Thilo Wack Head of Existing Product and Test Lab| optimed Tholey-Hasborn, Germany
Though it is already some time that I have read Goldratt's book, I'm quite sure that the main message was not about crashing the schedule by shifting ressources, but about not to buffer each activity, instead using strategically placed buffers to protect the critical path in case of single projects and staggering multiple projects in a such way, that the bottleneck ressource is always busy but does not work on multiple projects at the same time, as multitasking and too much work in process reduce the throughput of this ressource which is the limiting factor for all projects.

Please Login/Register to leave a comment.

ADVERTISEMENTS

"Chaos is a friend of mine."

- Bob Dylan

ADVERTISEMENT

Sponsors