I think this might be the first goverment case of a large organization trying to execute a publicly facing software project and failing. For decades the goverment didn't do public facing benefit projects. If this all happened in the 90s you would have to sign up using paper forms and although it may have been slow and inconvenient by today's standards that's what the goverment had experience in doing, it probably would have worked just fine.
I think software/web centric failures like this are going to keep happening. Few organizations, especially those whose primary business isn't software, are good at implementing huge software projects. Most management doesn't know how to run software projects, budget departments dont know how to account for software projects. If the Social Security administration has a huge backlog of applications they just add more people to the workforce until they work through it. Now everything is different, it doesn't matter how many people and how much money you throw at it, it's going to talk a while to fix. Very few people in goverment, and very few members of the electorate understand how a software project is run, hence a "surge" to fix the problem. People understand that concept, they imagine tons of nerdy looking guys flowing into some building and typing furiously at a keyboard until the problems go away. Good imagery, not really accurate.
I'm actually really amused by all this, it's my job playing out on a national stage. Terrible software estimates, contractors failing to live up to contracts, unrealistic timelines, poorly understood requirements, angry management demanding all hands on deck, and unhappy users. Maybe now software management will become an academic subject and mandatory study for MBAs and such.