2010 US Census and Project Management

We know that many projects fail, perhaps the more interesting follow-up question is why this happens. Following on from investigations of project failure at the Sydney Opera House and the H1N1 Vaccination Program this post examines the 2010 US Census which has experienced several project management problems in recent years. The US Census occurs every ten years to count the number of people in America so as to inform policy discussions, allocate budget and apportion seats to the House of Representatives.

Whilst it’s true that the US Census will happen (a delay to the program would be illegal) elements of the project are a failure. One of the goals of this census was to use automation to “improve coverage accuracy and efficiency”, in part by providing 500,000 handheld computing device to eliminate the need for those walking the streets collecting census data to print out questionnaires and maps. This process was “relying as never before on contractor provided technology”. $3 billion of the $11.5 billion census budget was to be spent on automation including the devices, which cost approximately $600 million. However in early testing in certain locations these devices experienced 27% downtime as well as other issues.

Reports from the US Government Accountability Office showed “an increased probability that the system would not be delivered on time and within budget or perform as expected.”

This situation occurred for the following reasons:

Lack of clear requirements

“The contractor is overwhelmed by a substantial increase in requirements having thousands of unreconciled (that is, not validated) requirements.”

Poor risk management

Some risks have been identified some risks, but there is no formal process or resource allocation to mitigate them should they occur. “Because they did not develop complete mitigation plans, the project team could not ensure that for a given risk, techniques and methods would be invoked to avoid, reduce and control the probability of the occurrence.”

Partial cost management plan

The program had initiated Earned Value, but not selected detailed performance measures to implement full cost management.

Executive reporting and communication gaps

The review calls for reporting on a “periodic and event driven basis”, but there was no evidence to document that risks were discussed with executives.

Of these issues the primary one appears to have been requirements management, because of the reliance on a vendor to provide the technology, this was a critical part of the process. It is not enough to give the vendor requirements, this was happening. Indeed the vendor received thousands of requirements, the need is for consolidation and validation of requirements.

It is likely that imprecise requirements is what caused cost overruns. Precise requirements could also have supported risk management because the timing of requirements and the mitigation strategies if they were not met could have been part of the process.

Whilst project management is a complex and interconnected discipline, it appears that similar to the example of the Sydney Opera House, imprecise requirements and scope management were a significant part of the problem.

2 responses to “2010 US Census and Project Management

  1. Pingback: The Failure Of The FBI’s Virtual Case File Project « Strategic Project Portfolio Management

  2. Good work and description

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s