The Billion-Dollar Website
stoborrobots writes: The Government Accountability Office has investigated the cost blowouts associated with how the Centers for Medicare & Medicaid Services (CMS) handled the Healthcare.gov project. It has released a 60-page report entitled Healthcare.gov: Ineffective Planning and Oversight Practices Underscore the Need for Improved Contract Management, with a 5 page summary. The key takeaway messages are:
- CMS undertook the development of Healthcare.gov and its related systems without effective planning or oversight practices...
- [The task] was a complex effort with compressed time frames. To be expedient, CMS issued task orders ... when key technical requirements were unknown...
- CMS identified major performance issues ... but took only limited steps to hold the contractor accountable.
- CMS awarded a new contract to another firm [and the new contract's cost has doubled] due to changes such as new requirements and other enhancements...
Non technical people are not competent to commission technical work from technical people.
If you (as a government or large company) don't have your own technical people on staff to oversee the process and comprehend or write the specs, you're doomed. The contractors know well how to milk a cash cow, simply by adhering to the specs written by people who don't understand how to write specs.
I should use this sig to advertise my book ISBN-13 : 978-1501515132.
it was a giant clusterfuck like many people on both the left and right were claiming way before launch. the site was NOT ready for prime time (the back end still is not 100%) and it never should have been launched when it was.
also, water is wet
have you seen my sig? there are many others like it but none that are the same
I don't work for a company that made the mistake of getting involved in that nightmare.
who are working round the clock to skim money from a project,
are still unable to run up costs like a government project gone off the rails.
Happiness in intelligent people is the rarest thing I know.
Ernest Hemingway
Somebody had to take the fall, and I guess they found the one group who didn't do the proper amount of CYA. Actually enumerating the failures and irresponsiblities of the various parties involved from the politicians down to the subcontractors... would have been too much work.
I guess they will just fire 1-2 guys and move the rest to other projects like "Heathcare.gov support" and file this report some where the sun never shines.
The key takeaway from the report is that nobody will be personally held to blame for the incompetence (at best; corruption and nepotism at worst) of the process and end result.
No punishments or consequences, all around!
-Styopa
between that and most private sector projects?
Except for technical companies, almost every large project during my 30 year IT career had the same issues and reasons for failing.
Don't hire people who have failed multiple projects in the past just because they were friends of the Obama campaign. At least that's what my finding determined.
Put the money for the contract, plus 10% into escrow. Every 10% into the projects completion you get 10% of the money. If you cannot complete it for that price, that is on you, not the tax payers, learn to better account for your work. If you can show that it was due to the government itself then that is what the extra 10% is for, if not and you fail the project we still got that amount of work done and can pass it to the next contractor in the bid to start working on. I am so tired of hearing about these massive cost overruns.
When you cant win, ad hominem.
America hired a man to run the country who never even managed a McDonalds.
Why would they vet their contractors (or contracts) any better?
Any one else think the article might be about a retina version of:
http://www.milliondollarhomepa...
How many millions did this investigation and report cost?
Zoid.com
> almost every large project during my 30 year IT career had the same issues and reasons for failing
They spent a billion dollars to post lorem ipsum https://www.healthcare.gov/med...
If almost every large project you're involved with is similar, we've learned one thing: Don't hire Chadster!
Anyone in software would understand the idea of code reuse. Instead the "billion dollar website" was re-implemented at the state level in many locations. Way to go politicians!
Scope creep/requirements instability are the root cause of nearly every failed contract I've seen.
Whenever a government contract fails, the public always blames the contractor, but if you look a little closer, there's almost always a significant customer role in the failure.
See VH-71: Within days of contract award, the White House pushed the Navy to add a bunch of new requirements. Pretty much, "We can't tell you why these are needed, but trust us, they're needed or THE TERRORISTS WILL WIN!" - This was the Bush-era White House, and that administration pretty much got anything they wanted with the "OR THE TERRORISTS WILL WIN!" argument. Lockheed was on time and within budget for Increment 1 (which was being built to the original contract requirements) but Increment 2 was becoming a massively overpriced flying tank due to scope creep/requirements instability and that killed the entire program.
See JSF: A major cause of issues on that program has been prioritizing the Marine STOVL variant over the others, even though that should be the LAST one due to it being the most complex/highest-risk variant.
CMS made many risky decisions in order to meet their goals, such as the use of "cost-plus-fixed-fee" contracts in the bid process and an Agile software development model, which was new to CMS.
As Figure 5 from the study, included below, shows, the Requirements, Analysis and Design stage of the project went from the originally scheduled three months to a year[...]
[... cutting] Operational Readiness Review from seven months to one. Yes, one. They reserved enough testing time to realize just how bad things were, and then they launched anyway.
Let's see...
Big up-front design? Check!
Scope creep driving increased redesign time? Check!
Implementation delays and compresses test phase? Check!
I guess they were using LAFABLE as their process.
Sounds remarkably like the Myki public transport ticketing system with it's associated blow-out to 1.5 Billion dollars https://en.wikipedia.org/wiki/... Although arguably Myki downgrade from the previous ticketing system. Clearly, planning and careful tendering and contract wording are vital in these big projects to hold the winning contractor to account, no changing contractors half way through or half arsed planning phase. Maybe it's just my thinking as an engineer, but so often these projects take on such a life of their own, what is really needed is a highly skilled and capable small core team of engineers and designers who build a working prototype and are able to make well thought out fast decisions on the move, then once it's been thoroughly tested, the big rollout happens, also with their oversight, you don't need huge numbers of program managers, project managers or project coordinators and nary a MBA should be in sight, you need people with the skills and knowledge to deliver the project, driving it, and only then farm out delegation work to other teams for specific deliverables to realise the bigger project.
Oh look, yet another great idea turned to shit with terrible execution. The hallmark of the Obama administration, and sadly the Bush administration too. I really hope this is not a trend with the new generation of politicians on both sides of the aisle.
Really, we want to complain about a website that cost a Billion? This is the United States Government, full of waste, fraud, no-bid contracts, and shit spread out out over every state so that ever senator and congressman has his slice of the taxpayer slush fund.
Witness the F-35 Joint Strike Fighter, an aircraft nobody needs, trying to fill too many roles, and was supposed to save our armed services money by having one plane replace many planes.
Except it's billions over budget, still doesn't work (and might never work), and is expected to cost more than a Trillion dollars before all is said and done.
Meanwhile the aircraft is being usurped by drones, which are cheaper, easier to deploy, and may fill all the roles we'd ever need this crazy ass jet for. And we're trying so hard to make it stealthy, meanwhile as pointed out in a slashot article a few weeks back, long wave radar will find the plane just fine.
And yet the Pentagon continues to shovel more money into the project because -- guess what, there's no "plan B". This is the people we depend upon to strategize for us in times of war, and they have absolutley no fall-back plan. Brilliant.
If telephones are outlawed, then only outlaws will have telephones.
CMS bows to congress who bows to the owner of congress = Big Pharma and more xxx.Inc's
who do you suspect issues the orders to CMS? I am very skeptical, to say the least
Probably this project came off just as planned.......
From the article:
QUOTE
The Accenture contract to take over the FFM development project was a one-year, sole source contract for $91 million for one year, and even that contract has exploded. As of June 5, CMS had obligated more than $175 million to the Accenture FFM contract.
END QUOTE
These contractors are a joke,. IBM has literally billions of failed projects all over America, most of them with some state government, DMVs BMVs etc etc. Look it up. Who is Accenture ? Accenture is Arthur Anderson by another name. Same fucking deregulation seeking, government tit-sucking sociopathic scum , they just changed their fucking name after they blew up America's economy with the Enron debacle in 2000.
http://www.zdnet.com/blog/projectfailures/erp-train-wrecks-failures-and-lawsuits/12055
http://www.businessinsider.com/2009/2/sap-clueless-consultants-from-accenture-and-ibm-giving-us-a-bad-name-sap
http://studentunionofmichigan.wordpress.com/2013/11/20/the-university-of-michigan-accenture-and-shared-servicesast/
These "consulting" companies smell a mega contract with the government and sail into port with slave ships filled with H1Bs with "Learn how To Program in 390 days" tucked into their knapsacks, knowing that the government will be too embarrassed to admit how much it's actually costing as the overruns start piling on. They bill the fuckshit out of the taxpayer and after they have that in their pockets, it all goes to court and the government is left with egg on its face while the filth defend themselves using the government's own money, "settle" the case with non-disparagement clauses everywhere then just roll on to their next "implementation".
http://accentureischeatingonitsclients.blogspot.com/2009/12/three-ways-accenture-is-cheating-on-its.html
http://www.pcworld.idg.com.au/article/445543/microsoft_accenture_joint_venture_avanade_sued_over_alleged_erp_project_failure/
http://spectrum.ieee.org/riskfactor/computing/it/bridgestone-sues-ibm-for-fraud-in-600-million-lawsuit-over-failed-it-implementation
Why does anyone hire these fucks in the first place? IBM et. al. should just be banned by law from any more state, local or national contracts and ditto with Accenture. Look it up i you don't believe me. This is the worst of the worst of sociopathic capitalism, right up there with Wall Street's credit default swap and collateralized debt obligation bullshit. This is the fleecing of America by what amounts to organized bands of thugs.
http://news.techworld.com/applications/3410597/ibm-faces-lawsuit-over-failed-sap-implementation/
http://itknowledgeexchange.techtarget.com/sap-watch/failed-erp-implementation-watch-ibm-named-in-lawsuit/
http://www.eaconsult.com/2013/12/20/with-friends-like-these-uncovering-responsibility-in-avons-rollout-failure/
http://blogs.wsj.com/cio/2013/08/06/pennsylvania-nixing-ibm-tech-contract-running-60m-over-budget/
I am just a technical guy, not the one writing business requirements, doing project management or signing off.
My point was, it is a general problem with how large technical projects are done and most "fail" because of the exact same reasons. This is not intended to start a discussion on techniques/methodologies.
I'm not trying to defend, it's just an observation.
Of course governments should be better at spending public money, but how can they be better when most organizations follow the same patterns and practices.
For the record, I don't work with or for any organization involved with that project.
Until President Obama repents of the great sins he supports, including abortion and the homosexual agenda, he will never have success at implementing anything! He has to first start with fixing the areas where he is morally wrong personally before he can successfully implement any scheme as grand as health care reform, because sound-mindedness does not come without a desire to obey the very basic precepts that God has layed out as Law first. And sound-mindedness is a prerequisite to knowing how to properly communicate information behind specifications and following-through with semantics refinement.
But don't take my word for it... you can read it in a book, the King James Version of the Bible. And if you disagree with this, you just take your diagreement to God and see where it gets you! But you have already received the message of the Gospel of Jesus Christ and are treading dangerous waters if you don't understand the plain truth that sound-mindedness first requires a desire to obey God out of love.
Normally, in order to solicit a project of any appreciable size, (over 100K) the government is required to produce a detailed SOW (Statement of Work) that defines the scope and goals. As projects get bigger (over 100M) the SOW begins to get more and more generic, but the accompaning Work Breakdown Structure (WBS) gets more detailed, and much much longer (five, six, sometimes as deep as eight or nine sub-sections) Each sub-section may generate dozens of Task Orders (TOs). Task Orders are what get assigned to contractors to work. If the upper document is vauge, or poorly thought out, or poorly defined, then the individual TO may be nonsensical.
Okay... so who is writing this nonsense? Well, the Government can't have the contractors who will be doing the work come up with the work they will do. (That's putting a fox in the henhouse.) So the Government will sometimes turn to a special type of contractor called a SETA (Scientific Engineering Technical Adisor) or FFRDC employee (Federally Funded Resarch Development Center) to develop the approach and SOW, WBS, and sometimes even write the TO. A SETA or FFRDC is specially recognised in that, they (and their respective employer) are expressly forbidden from bidding on or performing work on ANY project for which they have acted as a SETA or FFRDC. It's a classic case of conflict of interest. And, usually these guys are pretty good. There was no SETA or for the Healthcare.gov website. It wasn't considered a "technical" project (like building a moon-lander) so... that was probably the first mistake.
The second mistake is that the people in Government who normally get tasked with writing the RFPs SOWs and evaulating them are usually the same people who aren't um... "smart enough" to figure out how to get out of it. (LIke the jury-duty joke) They's also the same folks who get tasked with evaulating the proposals that come back... again... not the sharpest tools in the shed. So... there's plenty of blame to go round.
The absense of personal accountability in Government encourages irresponsible behavior. But, too much accountability encourages paralysis. (I'm not signing off on that!) So until we figure out how to fix that too... well... this is just going to keep happening.
why fall back when you are falling all over cash?
Sure, many people make the same mistakes. I'd hope that for a BILLION dollars, you could hire a couple of project managers who are actually competent. Plenty of companies have incompetent people, but plenty have lots of competent people who successfully complete projects - Google, eBay, Facebook, and a thousand other companies are competent at large scale IT projects.
If, like most projects, your budget is around $100K, you might end up with some typical incompetents in key positions. For a billion bucks, you should be able to have really, really good people in the key leadership positions making sure the project gets done. Was the person running the healthcare.gov project competent? Nobody was running it! I hope that's not like your typical project, I hope you actually HAVE a project manager at the head of most of your projects.
> Of course governments should be better at spending public money, but how can they be better
#1 Put someone in charge of the project.
#2 Choose someone who has successfully led a large project before.
Note however there is one very important point missed in all the rhetoric... That of changing specification coupled with muddied/stratified change management. This issue sits squarely on CMSs shoulders and is absolute poison to any IT project of any significance...
It was the politicians more than CMS. Not that CMS didn't have its share of problem generation but folks in the administration doing political recalculations on what the user interface and functionality should be like probably made this problem far worse than your normal federal project.
Wasn't there some last minute change ordered by the administration not to show the unsubsidized policy price, so now the site had to integrate with various other agencies and exchange a lot of personal information to calculate an accurate subsidized price? Note that the subsidized price is absolutely unnecessary for comparison shopping. A person's subsidy is a constant, it does not change the price difference between policy A and policy B. If A cost $X more than B before subsidy it will still cost $X more after subsidy. It was purely a politically motivated change to avoid sticker shock on pricing.
The worst part is there is no reason why the Obamacare websites even need to exist.
Obama could have just told everyone to buy their insurance on einsurance.com and to get the subsidies when they filed their 1040.
I can't be the only one shocked, SHOCKED to discover, the government is inefficient and wastes money. I mean, after the staggering success of everything else it operates — things like US Postal Service or Amtrak — it is certainly most disappointing to encounter a government program, that fails to live-up to our high expectations.
Nay, this may even chill our collective enthusiasm for making food and shelter a government's responsibility too — you can't be healthy without nutrition and a roof above your head, can you, so it only would've seem natural to further expand the government's omniscient and benevolent control into that direction. But not any more... Not quite...
In Soviet Washington the swamp drains you.
Another is His infinite string of divine victories. All dissidents are of course racist.
It would be nice if someone has a compiled timeline of events starting with extremely uncoordinated writing and passing of the law, to the point where technical specs were released to the contractor, when the actually flow of information and final HHS rules were announced, up through go live and the fixes being implemented after go live.
From what I've read/heard there was little to no work being done from 2010 when the bill was signed into law up through 2012. The administration purposely withheld information about Obamacare from the public and from the contractor due to the election year (2012) and didn't want bad press. Once the election had passed the government released more specs and information to the public and to the contractor on how the website was supposed to function. That's when we found out the dirty little lies and secrets. It's damn near impossible to build a website/service to handle 300M+ people in 6 months, but that's what our government did.
This whole bill/law/implementation has been bungled so badly by:
- the incompetent people who wrote it (bureaucrats with no understanding of health care and did not consult people from the health care industry)
- the incompetent people in Congress who blindly passed it without reading or understanding the devastating effect it would have
- the incompetent administration who continued to lie about how the law affected the citizens, and took no ownership of this massive project
Can anyone imagine a scenario where this could have been handled worse? Every step along the way was screwed up.
"A plan fiendishly clever in its intricacies"- Homer Simpson
And what if the doctor has sworn an oath to provide medical care? What if they have contract with the surviving entity? What if they've been a member of the AMA and agreed to be bound by its code of ethics? What if they've chosen to live within a society, and be bound by its laws?
Right now, as far as I know, you're not being compelled to become a doctor, and your preposterously constructed hypothetical situation doesn't address that doctors are already bound by these oaths and principles of their own accord.
Is it wrong for a person to be bound by his or her own word? When do they get to break or bend it?
There's a reason why medical ethics classes are part of the curriculum at every medical school I know, and while I don't know if they bring up your specific iteration, they surely do cover ones similar enough. The duty of care covers disasters, and it remains in effect.
And the choice is simple. Don't like it? Don't swear the oath. And probably best if you don't try to act as a doctor, you could get in trouble if your standard of ethics doesn't measure up. Why? Probably at the foundation level, because people who behave in the fashion you suggest, are considered dangerous to be around. They're bad for everybody else in reputation alone.
(And no, physicians aren't the only ones with such obligations, many professionals are under such strictures, however, we need not digress into them.)
Sounds like "waterfall" to me.
Mine says, "Lifewise"
It also says, "Essential Silver 2500 HSA" which defines it as one selected from the website. The network name probably identifies it also. Not to mention the 4 other id numbers on the card.
Not sure why a doctor would care as they seem to be rather normal insurance plans but they could tell if they wish.
Medicare/Medicaid are a whole other story. Often patients don't have the copay and that is profit for many procedures/items due to low payments on SOME things. (and some are still overpaid) Often the additional paperwork and the threat of an audit put many off accepting those. Or, as in my case, All of the above plus the fact I can't afford the bookkeeper JUST for 3rd party billings.
I currently sell medical supplies and did the books for a medical supplier for almost 20 years. ...don't try this at home!
Survived a Medicare audit and a Sales Tax audit with no penalties
I used to work for NAVFAC, the U. S. Navy version of contract management for construction projects. Though there was a lot of bureaucracy involved, the planning and design phase always had plenty of experts to ensure the specifications were above most commercial standards (LEED certifications, military requirements, utmost safety requirements, etc...) Though many aspects of the process used archaic technology (lots of paper forms, area expert controlled word documents as best practices,...), the end result was that most projects ended up being completed on time and on budget (though the start sometimes got shifted so the review could be thorough ... unless October 1 was coming, but that is a different subject - or maybe not, this project had similar time deadlines). A lot of this success was due to savvy construction managers doing appropriate "horse-trading" with contractors to avoid the lengthy change processes (which could delay anywhere from a day to 12 months). When you have (non-technical) contract managers who don't know the reasoning behind the requirements, they have little recourse but to go through the official processes to resolve complex issues... _This_ is where you get your delays. For the most part, a good hour spent in design/planning will yield ~10 in production, but it is important for the project manager to be intimately involved so this wisdom can actually be _useful_. I can attest to my own anecdotal experience and my observation of others, that coming into a project at production phase is more than just a steep learning curve; some things just have weird historical issues. Here are a few that I ran into after another CM was transferred elsewhere:
- endangered species in the area
- abandoned toxic waste in the soil
- asbestos
- this site used to be a WW2 bombing range and guess what?...We found a bunch of unexploded ordinance.
- hurricane damage
- tornado damage
...and I don't just mean the technical aspects, what I'm talking about is how the technical information to make the project work being spread across multiple organizations that do not necessarily share information much less have systems and methods in place for inter-agency cooperation. You can't come up with an adequate analogy between this project and any others, because there haven't been any similarly complex projects.
Yes, it feels good to bitch about how incompetent "the government" is, but THAT dialogue is always about a political agenda, and not a factually descriptive language.
When you rush a project and dump money into it your results are as expected. No political agenda and deceptions necessary.
And if the federal government can't improve its processes for such things, perhaps it will quit attempting them. After all, screw up enough things badly enough, and it'll run out of money, and go away. Such is the nature of failed institutions.
Oh, wait. That won't happen. Two reasons: IRS and Federal Reserve.
Of course, it could go away without running out of money. Two examples: Weimar Germany and Zimbabwe. The places were still there, but they had dramatic changes in management.
Such is the nature of failed institutions.
There's no time like the present. Well, the past used to be.