SoylentNews is people
SoylentNews
Stories about seriously mangled public infrastructure projects keep coming up and even the alleged super-efficient Germans are not exempt. But what would you expect when you change and expand the project while it is being implemented and when you use smaller contractors with no track record for projects like this? the BBC has the story:
As a structure, it looks impressive enough.
Until you pause, look around you, and absorb the silence. This is Berlin Brandenburg or BER, the new, state-of-the-art international airport built to mark reunified Germany's re-emergence as a global destination.
It is a bold new structure, costing billions, and was supposed to be completed in 2012.
But it has never opened.
BER has become for Germany not a new source of pride but a symbol of engineering catastrophe. It's what top global infrastructure expert Bent Flyvbjerg calls a "national trauma" and an ideal way "to learn how not to do things".
[...]Martin Delius, a former Berlin city politician who later headed an extensive inquiry into what went wrong, says those in charge decided "to give 30 to 40 contracts to smaller companies which they thought they could pressurise into giving them lower prices".
"They built a very complex controlling system which didn't work," he says.
Most disruptive of all were decisions to change the size and content of the new airport - while it was being built.
[...]New construction boss Hartmut Mehdorn made a list of all the faults and failures, Mr Delius tells me.
"Small ones like the wrong light bulbs to big ones like all the cables are wrong," he says.
The final total was 550,000 - more than a half a million problems to fix.
Maybe that builder who left a big hole in your dining room wall for a couple of weeks wasn't so bad after all? It wasn't like seven years later, was it?
(Score: 0) by Anonymous Coward on Tuesday July 02 2019, @09:55PM
Yeah, it's impossible to cover all the immense fuckups that we can find within soylent's text limitations. The morons who disbelieve every word that Brooks ever wrote are just one aspect of it.
One recent challenge I faced was outright sabotage from devs who somehow thought that death marches would be preferable to Agile - presumably they were more excited about the devil they know, than the reverse. Managed to get them around by pointing out that management had a choice between two options (because of politics, long story) and the options were: Agile and (some approximation of) DevOps, or layoffs and contracting a firm of indian IT people who promised the impossible for a song and dance. Faced with the alternative, precisely none of them left the company, and all of them decided to embrace an Agile system.
Surprisingly, none of them broke legs or caught cooties from Agile. Instead, after a couple of months of learning the ropes, they actually started to produce. Outsourcing averted!