Home > Articles > Process Improvement

What Went Wrong with Healthcare.gov and How Can It Be Fixed? A Suggested Reading List for Managers and Developers

Most software projects aren’t as complex as the ACA website, Healthcare.gov, but any software project can benefit from smart project management and development. Jess Johnson takes a look at some books about running a software project and recovering from failure, plus some specific guides for front-end optimization, scalability, security, testing, and refactoring to see how that advice can be applied to healthcare.gov.

Looking for a different subject? Take a look at a directory of all of our Developer Reading Lists.

Like this article? We recommend

Healthcare.gov has been plagued with issues since its launch. Although the failures of healthcare.gov have been much more visible and publicized than those of most other IT projects, the reality is that this is a typical outcome for projects of this scale. One study shows that 34 percent of projects are unqualified successes, 15 percent are complete failures which were abandoned before completion, and the remaining 51 percent, like healthcare.gov, fall somewhere in between.

Large scale software projects all tend to face the same classes of issues, so there is already a large body of research material, books, and other resources that cover the problems being faced by healthcare.gov. Let's look at some books about running a software project and recovering from failure, plus some specific guides for front-end optimization, scalability, security, testing, and refactoring to see how that advice can be applied to healthcare.gov.

Rapid Development Rapid Development: Taming Wild Software Schedules by Steve McConnell

Rapid Development is a brilliant guide to running a software project in the real world, where tradeoffs need to be made between defect rate, cost, and development time. There is advice on estimation, scheduling, risk management, project lifecycles, and team structure. These are topics that are common to all software projects, but which have been especially problematic for healthcare.gov.

There is an entire chapter in Rapid Development devoted to project recovery (chapter 16), which is the immediate focus of healthcare.gov.

Peopleware Peopleware: Productive Projects and Teams, 3rd Edition by Tom DeMarco and Timothy Lister

Peopleware looks at the sociological side of software development, which it identifies as the main source of failure for IT projects. The authors' research shows that problems with communication, staffing, motivation, and other sociological factors are vastly more likely to cause a project failure than technical factors.

Healthcare.gov is a project where there are reportedly more than 50 different contractors, all working on different subsystems, with limited intercommunication between teams. There has been much blameshifting and unwillingness to claim responsibility for glitches or failures from management. With this type of toxic sociology, it is surprising that healthcare.gov works as well it does.

The Mythical Man-Month: Essays on Software Engineering,  Anniversary Edition, 2nd Edition The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition, 2nd Edition by Frederick P. Brooks

The Mythical Man-Month is one of the classic works on software project management. This is the book that coined Brooks's Law: adding manpower to a late project makes it later. The idea is that once the team is above a certain size, the communication overhead of adding a new person to the team will swamp any gains that person is able to make in moving the project forward.

This principle will surely come into play during the "tech surge," which is adding manpower at all levels, from developers to management.

>High Performance Web Sites: Essential Knowledge for  Front-End Engineers High Performance Web Sites: Essential Knowledge for Front-End Engineers by Steve Souders

This book is a list of best practices for optimizing the front end. Yahoo's YSlow test is a standard metric for measuring front-end performance, and High Performance Web Sites covers much of the same material along with implementation details for each tip.

Although it is now clear that healthcare.gov's main problems are elsewhere, there is plenty of improvement to be made on the front end by applying the techniques listed in this book: combining and minifying JavaScript files, using a CDN, setting up HTTP headers for caching, and so forth. These optimizations are fairly low hanging fruit; they are easy to implement and the speed gains are usually significant and easy to measure.

Scalability Rules: 50 Principles for Scaling Web Sites Scalability Rules: 50 Principles for Scaling Web Sites by Martin L. Abbott and Michael T. Fisher

Scalability Rules is a technical overview and reference on scaling web sites. Any site the size of healthcare.gov needs to address scalability issues such as caching, database optimization, horizontal scaling, and designing for fault tolerance and graceful failure, all of which are covered in this book.

In particular, healthcare.gov integrates with a large number of external legacy systems, and this appears to be the cause of much woe for the healthcare.gov team. Asynchronous communication would be a natural solution to this type of problem, and Scalability Rules has an entire chapter (chapter 11) devoted to that topic.

24 Deadly Sins of Software Security: Programming Flaws and  How to Fix Them 24 Deadly Sins of Software Security: Programming Flaws and How to Fix Them by Michael Howard, David LeBlanc, and John Viega

This is a high-level overview of the most common causes of security issues. It divides vulnerabilities, or "sins," into the broad categories of application, implementation, cryptographic, and network.

There haven't been any publicized security issues with healthcare.gov, but high-level members of management have expressed a somewhat cavalier attitude toward security. Any project that handles sensitive information, especially one of this magnitude, is bound to benefit from a careful security review. Working through the "sins" in this book and following the recommended process for code review, testing techniques, and defensive measures would be a great start.

Lessons Learned in Software Testing: A Context-Driven Approach Lessons Learned in Software Testing: A Context-Driven Approach by Cem Kaner, James Bach, Bret Pettichord

A few of the other books in this list touch on testing, but because a lack of adequate testing was such an important issue with healthcare.gov, adding a dedicated reference to the list makes sense. Lessons Learned in Software Testing is a collection of wisdom, observations, and tips packaged into almost 300 different lessons. Topics covered include planning a testing strategy, managing the testing project, automating testing, and techniques for testing.

Refactoring: Improving the Design of Existing Code Refactoring: Improving the Design of Existing Code by Martin Fowler, Kent Beck, John Brant, William Opdyke, and Don Roberts

Refactoring describes a systematic way to take a bad design and rework it into something better. While much of this book is specific to Object-Oriented Programming, the central idea of actively working against entropy in order to improve the original design over time is a valuable one to any software project.

If the healthcare.gov codebase really does contain 500 million lines of code, as has been reported, then significant refactoring and dead code removal will need to be a fundamental part of any strategy to put the project back on the rails.

There are many more excellent books on software development that can provide insight into the healthcare.gov malfunctions. The books in this list are just a jumping off point for learning about each of the major areas where healthcare.gov has failed to meet its goals and to provide some solid ideas for moving forward.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020