Government Executive had an interesting article on the Census Bureau handheld project problem. In an interview with Government Executive, agency director Steven Murdock said that there was a "combination of events" that contributed to the problems, and he spread the blame among the Census Bureau as well as the contractors.

Director Murdock also said in the interview that he didn't want to dwell on past problems, which I can fully understand. Right now, the agency has to make certain that the 2010 census can be properly conducted, so all efforts need to be focused forward.

However, this also is the best time to really do a comprehensive post mortem on why the handheld project went south, especially focusing on the decision making process that took place along the way and how it addressed (or didn't) the various technical, contractual, political, managerial, etc. sources of risk.

Right now memories are the most clear, emotions are still raw, and the paper trail still likely exists. By this time next year, revisionist history will have set in, people will be circumspect, and critical memos, reports, etc. will be finding their way into the shredders if they aren't doing so now.

If the Census Bureau - or the Office of Management and Budget - really wants to understand why big government IT projects fail and how to begin to avoid the inevitable next one, it needs to do some investigative case analysis on real projects to look for both systematic and systemic sources of risk.

The Army has a Center of Army Lessons Learned to thoroughly and objectively look at what goes right and what goes wrong across Army operations and publishes that information as widely as possible - it is high time the government has something similar for IT projects.

Latest Blog Posts