Imagine politicians with a stake in the project's failure hearing that: they will go full Benghazi on it.
Imagine politicians with a stake in the project's failure hearing that: they will go full Benghazi on it.
You don't want to be seen having failures in your project (even small, agile failures that are for the good)... but you don't care if the project succeeds.
If you can plan out a waterfall project that won't complete until you're "out of office", then there is no negative consequences for you... even if you KNOW it will fail once you're gone, that's the next guy's problem.
Sad, but true.
Back in 2004 or so, I heard of a major company that only updated their website once a year. Even then that was considered ridiculous. Consumer expectations have shifted massively; plenty of places now release every week or two.
I have hope that the government culture could shift similarly, so that software projects that don't deliver anything for long periods are seen as troubled no matter how many Powerpoint decks and GANTT charts they produce in the meantime.
And I think the way to change that culture is by having enough projects that deliver early and often, so that people say, "Well, those guys are shipping monthly. What's wrong with your team?" So instead of keeping people from being blame-y, we get them to be blame-y about long project cycles.
I think that's definitely happened a fair bit in industry, so there's some chance it will happen in government, too.
If it's either a failed public project, or spending millions of dollars (that can be spun as creating jobs), what do you think they're going to take?