The problem with using the private sector for public sector work is that private sector IT people, in my experience, prefer testing in production.
I work in software development. I don’t know what people you have worked with, but every single employer I have ever worked with and worked for abhors the idea of “testing in production.” It is expensive and extremely embarrassing. It is a well known maxim in software development that the later in the development cycle a defect is found, the more expensive it is to fix it. And no developer ever wants to spend more than they have to.
In my experience, it is the client that prefers testing in production, not the developer. More below.
No one wants to be responsible for a delay so the rollout proceeds without adequate testing.
I worked for several years at a company that developed products 3rd parties. A guy comes in, thinks he has the next great idea, and we turned it into a product. We would quote them for design, implementation, and testing. When they saw the amount of money they’d have to spend on testing (usually somewhere between 50% to 66% of the total cost), they would balk. We’d explain to them that it was extremely important that the product be thoroughly tested before it was made available to the public.
They would say things like “Why do you need so much testing? Are you guys not good at what you do?” Or “We can live with a few bugs, how far can we whittle down those hours and only have a few we can work out later?”
And in all those years working with clients, only 1 agreed to the total cost. The other pushed for much less testing before release. And inevitably, those client would come back to us and ask us to fix the issues found post-release. And it would cost more.
Our VP of engineering during an internal meeting presented a post-mortem of the last several projects we had done. He compared the amount of money a company spent on testing if testing was done pre-release (only 1 sample) and post-release. The pre-release testing cost was a fraction (as a percentage of overall cost) of the post-release fixes/testing. And this became new data to use when selling to clients the need for testing pre-release.
People can berate the government all they like, but the reality is that this is private sector work.
In this case, the government is the client. And in my experience, it is the client that pushes for testing in production. I don’t doubt the government pushed for releasing on schedule, and overrode objections from the developers about the need for more testing. And I’d bet a $100 that the developers told the government they shouldn’t go live until the testing was done.
It doesn’t matter if it is private sector work or public sector work. In both cases the government is the client. And the client wanted schedule over quality. And, like most clients who do this, they get neither schedule nor quality.