6 ms·
So, the fiasco continues. A cynical person might think first contractor failed on purpose, so that the second bunch of "experts" could be brought in to fix it.
by ams6110 13y ago
So, the fiasco continues.
A cynical person might think first contractor failed on purpose, so that the second bunch of "experts" could be brought in to fix it. One system for the price of two (or more, "expert troublshooters" don't come cheap). I'd really like to see a transparent accounting of who is getting paid, and how much, to implement this so-called website.
- KevinEldon 13y agoI don't think the cynical view makes a lot of sense. The original contractor is likely billing for hours to fix the site now. Bringing in additional experts doesn't benefit them. A failure of this scale and visibility isn't going to help their business reputation and if they lose the maintenance contract on the site they're likely to be out for millions. I can see bidding low with the expectation of making a killing on change orders (I think the contractor succeeded at that), but outright failure to deliver doesn't make a lot of sense. I think like most IT projects you need to look at the management team in charge and the decisions they made to understand if this failure could have been identified and avoided.
- mgkimsal 13y ago> A failure of this scale and visibility isn't going to help their business reputation Do big failures really hurt people or companies all that much? At some point, you're dealing in a realm in which relatively few people even play (or perhaps even want to play) and you may be the only game in town anyway. Bankers/CEOs who lost millions were still given large bonuses with the reasoning that "we wouldn't be able to find anyone else to do their job". Well... I could certainly lose millions faster than many of them, and I'd do it for half their bonus, thereby saving the companies money :)
- yen223 13y agoThat's something I used to wonder too. I used to work for a company that had a number of highly-visible failures, the kind that gets reported in the news. They somehow still managed to score multi-million-dollar contracts. I suspect having a great sales team is more important that having a great engineering team.
- protomyth 13y ago"Do big failures really hurt people or companies all that much?" Some folks do get black balled[1], and companies will liquidate from time-to-time, but in the end, I really cannot think of anyone that didn't end up richer except the poor souls the companies hired. These days, most of them just switch to another company and continue the cycle. 1) if your name is know to a career, high-level administrator in a bad way, expect a lack of contracts
- mlangdon 13y agoI'm perpetually puzzled that people in tech keep seeing nefarious purposes behind this failure when it sounds like every failed project we've heard of. Moving targets (how many states, how many users), feature creep, managers with no understanding of the undertaking, too many managers, and no time for testing and debugging. It's not evil, it's just incompetent and embarrassing.
- siculars 13y agoall the states. all the citizens. how is that not obvious? these are known knowns.
- tokipin 13y agoi thought healthcare.gov is for those states which opted out of the medicaid expansion (i'm not sure about this). it may have been the case that the number which have opted out was unexpected by an order of magnitude. i don't know if i'd buy this excuse though
- Spooky23 13y agoNo it's not. All states were supposed to have their own exchanges. 14 ended up doing it. New York after all sorts of political machinations agreed to run their own exchange at the 11th hour. (Supposedly "unprecedented" traffic also screwed up the NY exchange, which was also built by some big government contracting firm -- CSC)
- jussij 13y ago> It's not evil, it's just incompetent and embarrassing. And anyone who has worked in the industry over a long period of time will know that for big projects this closer to the norm than the exception. I've personally worked on one massive banking project in the 90s that turned into a billion (in today’s terms) dollar right-off and in that time I read of many other such disasters.
- dersen 13y agoAgreed. While it sounds cool to bring in a "dream team" of technical experts to save the day, it seems likely that additional non-technical issues are at play besides (or in addition to) the technical incompetence of the contractor. Here's an alternate scenario: 1. The government agency that hired the contractors does not completely understand the business requirements in a way that allows them to effectively communicate them to the contractor. This could be due to numerous factors outside their control such as changing legislation or perhaps because the ACA is so large (900+ pages) and relatively new that there are few experts who understand the minute details sufficiently to specify how the exchange should work. 2. New requirements emerge at the last minute, requiring the contractor to make significant changes. While it is recognized that additional schedule time would be needed to sufficiently implement and test the required features, there is enormous pressure (political and otherwise) to adhere to the October 1 release date, so the implementation of the features is rushed and QA is skipped. 3. There are dependencies on legacy government and commercial systems that are outside the control of the contracting agency and the contractor. The functionality of these systems impact reliability and performance, introduce strange bugs, etc. 5. The software is delivered on time but is woefully inadequate. While I wouldn't rule out the incompetence of the technical staff, these types of issues can often be traceable to problems that are more in the realm of management.
- thrill 13y agoNo point really. It's taxpayer money. It's limitless.
- hardwaresofton 13y agothis. But to play Government's advocate a little: That's also kind of how we got awesome things like GPS systems kinda fast.
- MBCook 13y agoPlus the Republican missteps on the shutdown/debt ceiling means that their best anti-Obamacare story barely got any airtime. And since there wasn't much airtime, there won't be much pressure to get to the bottom of it.
- Untit1ed 13y agoHaving worked on big government projects with big consulting companies, that's pretty unlikely. Government projects are usually undersold in order to win the tender and are subsequently delivered late and to a low standard, the difference is that they're rarely high-profile enough to get noticed by anyone who makes procurement decisions, and so the consulting companies' salespeople get to bid for the next one. I've seen program managers getting pretty nervous when senior bureaucrats start breathing down their neck - I'd have to admire the balls on one who intentionally fucks up a project while being personally scrutinised by the President of the United States.
- protomyth 13y agoYou do not want to embarrass an administrator as a contractor[1]. If there is any rule of government contracting, its that one. Large military contractors can get away with it because they are few and have much lobbying money. Smaller contractors should know better. I would be curious if this company dissolves in the future. I remember a company in the 90's that ticked off someone in HHS and the company was no more in about a year (had a really generic name with a common TLA, my notes are in a storage locker). 1) which should make you read very closely some government findings when it was a pet project of some longtime admin or Senator.