I've been seeing stories like this about out of control software projects as long as I've been working as a developer (so since about 1992). The conclusion is always that the root cause is either malice or incompetence - but it's awfully suspicious that software is conspicuously alone in attracting this much incompetent malice. Of course, we hear stories like this about general contractors, but they're the exception rather than the rule - for the most part, when somebody hires somebody else to build a house, they get a house and it costs mostly what they were quoted up front and takes mostly as long as they were told it was going to take.
While I guess nobody would take time to write about a software project that went exactly as predicted, my experience is that those are the exception rather than the rule, and the cases where a software project was accurately quoted in advance are relatively trivial projects.
I can understand why the people who are writing the checks want software projects to be predictable, but in 30 years of practice, I've never figured out a way to accurately predict them, nor have I met anybody else who could. I've met a lot of people who accuse me (and software developers in general) of malicious incompetence for not being able to foretell projects in advance, I have yet to meet one who rolls up their sleeves and says, "here, let me show you how to estimate this stuff accurately" except in very abstract terms like "first write down every task you're going to do, then write down how long each task is going to take, and then add up those numbers and voila! Estimate complete!"