Why Are Projects Always Behind Schedule?
priceonomics.com
Why Are Projects Always Behind Schedule?
1–10 of 111 posts
Re: Why Are Projects Always Behind Schedule?
#2Re: Why Are Projects Always Behind Schedule?
#3Simple: time is a resource, it is a cost. When one bids for a project, time is also taken into account when selecting a vendor. So, just as one tries to offer the best price and experience, the same goes for time. One knows that the project will most likely take longer but if that realistic timeframe is put into the proposal, there is risk in losing the contract. It is a safer bet to later ask for reasonable time ext…
Realistic proposals fail. An under-resourced under-priced and short-scheduled proposal is functionally approved by the customer-user, then signed-off as the cheapest/shortest option by the customer-payer.
The real negotiation is in the T&Cs for change management, scope creep, responsibilities for delays and the structure of payment according to milestones.
Re: Why Are Projects Always Behind Schedule?
#4Re: Why Are Projects Always Behind Schedule?
#5Re: Why Are Projects Always Behind Schedule?
#6Hofstadter's law + Parkinson's Law + Murphy's Law = Delay
"It always takes longer than you expect, even when you take into account Hofstadter's Law."
— Douglas Hofstadter, Gödel, Escher, Bach: An Eternal Golden Braid
Re: Why Are Projects Always Behind Schedule?
#7Re: Why Are Projects Always Behind Schedule?
#8Re: Why Are Projects Always Behind Schedule?
#9The reason is actually quite simple: when things go well, they can only go so well, but when they go bad, they can go really bad.
Or, in a more quantitative way: while each step of the project will be equally likely to take longer or shorter than median, the steps that take longer can take much longer, while the steps that go faster only have a limited potential for balancing out the delays.