[gahahaha]

Yea - I'm not really sure what the take away message here should be (although I found the article interesting).

I'm currently working at a late project right now that started early enough, but took too long to hire enough people to finish the project in time, and didn't use the time at the beginning of the project well enough to gather information about the current and future processes. Maybe that's an example of what the author means, but it certainly gets more complicated than "started too late" quite quickly...

[luckydata]

The message is "late software" is really a failure of decision making at the highest level that waffle on necessary things until they become necessary but move too late on it. I've personally seen plenty of that, so works for me.