9 best practices for successful IT projects

By , Network World |  IT Management, project management

Most often when the watchdogs at the Government Accountability Office are called into to check out an agency, process or project they are looking for something that has gone wrong. This week, however the group took a look at some government IT projects that have gone right and came up with some best practices other government agencies or in public corporations could emulate to achieve success in their own IT projects.

In the report, the GAO noted that planned federal information technology spending has now risen to at least $81 billion for fiscal year 2012.

MORE NEWS: Celebrating the birthplace of the Internet in pictures

"As we have previously reported, federal IT projects too frequently incur cost overruns and schedule slippages while contributing little to mission-related outcomes. Given the size of these investments and the criticality of many of these systems to the health, economy, and security of the nation, it is important that federal agencies successfully acquire these systems -- that is, ensure that the systems are acquired on time and within budget and that they deliver the expected benefits and functionality," the GAO stated.

After interviewing the CIOs and other department officials in the seven projects it identified as successful -- which included programs from the Census Bureau, Defense Information Systems Agency, National Nuclear Security Administration, Customs and Border Protection, Federal Aviation Administration, Internal Revenue Service and Veterans Health Administration -- the GAO came up with nine common factors that were critical to the success of three or more of the seven investments.

Those common critical success factors and a small example of each were:

1. Program officials were actively engaged with stakeholders. For example, Census officials stated that the workers on its Decennial Response Integration System (DRIS) were members of the integrated project team. Their responsibilities as members of the team included involvement in requirements development, participation in peer reviews of contractual deliverables, and review of contractor proposals, the GAO said.

2. Program staff had the necessary knowledge and skills. For example, VA officials told the GAO that the Occupational Health Record-keeping System (OHRS) program relied extensively on the subject matter experts' occupational health experience -- treating them as part of the development team and including them in decision making. Two investments in our sample even went one step further -- by selecting the program manager from the end user organization as opposed to an individual with an IT background.


Originally published on Network World |  Click here to read the original story.
Join us:
Facebook

Twitter

Pinterest

Tumblr

LinkedIn

Google+

Answers - Powered by ITworld

Ask a Question
randomness