>>81561947I can tell you have no experience with such projects. Not with the government and not on such a massive scale.
What you're saying is the basics of the software engineering of a cs grad that errbody learns in the kindergarten nowadays. And they made sense for an offline software project a number of years ago or small tools today, maybe, even.
Your line of thinking is in no way applicable to the huge scale LIVE projects, that have to ensure SECURITY first, functionality, stability, teaching the workers the basics of software, and so, and so forth, in parallel, while fixing and combating real-time issues, problems, threats, and cyber attacks.
Human factor alone makes any design workflow fly out of the fucking window, if you don't have stable e-mail servers protected by layers of nowadays AI spam filters, because Kevin the 63 year old moron from community garden planning or some such bullshit has opened a malicious spam e-mail and data in it containing worms (written by AI as of today, or with the help of).
Normally the news don't report it, but the amount of times the government was hacked and cyber attacked is staggering. When something bad does happen it usually is the human factor. But that's a tangent.
Not to mention that any change in data protection, or systems security at large, and so on, have to be voted on by the local politicians first. Because they'll be working with it. Their heads are at stake. A federal government can't just magically command everything and fix everything and give all of the guidelines for everybody. Maybe they should've invested in such a plan, but it doesn't exist. Because "local", read state, and then down to the town hall level, mini governments are all independent, yet must co-exist and cooperate efficiently at all times. Preferably anyway.
TL;DR: Anon, it is way, way more complicated than you think of it initially or imagine it to be.