DOD tries a new risk strategy
Critics say DOD’s chosen methodology lacks a portfolio management perspective
- By Peter Buxbaum
- Sep 29, 2007
Last year, the Defense Departments Business Transformation Agency examined the militarys record of implementing large automated information systems and found it rife with failure.
In response, BTA decided to test-drive a risk-mitigation methodology that has a proven track record in the commercial world. Its critics, however, say its effectiveness is diminished because it does not use portfolio management techniques.
BTA selected the Enterprise Risk Assessment Methodology (ERAM), which it derived from a commercial risk-management approach that uses cross-functional teams to interview key program employees.
Their job is to discover unnecessary program risks and issue risk-mitigation recommendations. BTA officials said they will use the methodology to find out why DOD is not realizing the capabilities it expects from commercial information technology.
The main purpose of ERAM is to figure out what is preventing us from realizing capabilities, said Paul Ketrick, BTAs director of investment management.
BTA is testing ERAM with nine programs. Officials chose those programs because they are still in the early stages of development, which will make it easier to change course, if necessary, Ketrick said.
The teams develop a risk hypothesis before interviewing project leaders. The hypothesis often changes as the interviews progress, Ketrick said. We often go down paths we never expected.
ERAM teams interview dozens of people to examine potential risks related to the contract, program strategy and requirements, technical factors, people, processes, and external factors. The objective, Ketrick said, is to get a holistic view of potential program risks.
Once the ERAM team completes its interviews, the group drafts risk-mitigation recommendations and discusses them with program managers before they become official.
The program manager takes responsibility for risk mitigation, Ketrick said. There may be some situations when mitigation is not advisable, such as when there is an immediate warfighter need. Thats the program managers call.
DOD expects to expand the use of ERAM to all new major business information systems. The department also is preparing to implement a business capability life cycle assessment program that will examine relationships and interfaces among information systems.
ERAMs major weakness is that is not a portfolio management tool, government auditors say. The Government Accountability Office has recommended that DOD improve its management of information systems by evaluating risk across a portfolio of capabilities.
ERAM is not a panacea, said Randolph Hite, director of IT architecture and systems at GAO. Efforts are now under way to better understand the nature and impact of program risks through the application of ERAM, he said. ERAM can be valuable in understanding and addressing program risks, but this tool is program-specific and not portfolio-focused.
Ketrick agreed that ERAM lacks a portfolio view. DOD will try to address Hites critique of ERAM by implementing assessments of business capability life cycles (BCL), Ketrick said. BCL will address how systems fit into the context of the enterprise, he added. BTA will launch BCL next month.
Although ERAM teams do not have the authority to enforce their risk mitigation recommendations, there can be dire consequences if someone doesnt want to follow them, Ketrick said.
The DOD Investment Review Board may find it necessary to implement a risk-mitigation plan and cut off funding to any program that refuses to adopt a mitigation plan. DOD officials also could suspend milestone development decisions or determine that the program is not compliant with the departments enterprise architecture.
If the program spends another dime under those circumstances, Ketrick said, someone will go to jail.Buxbaum is a freelance writer in Bethesda, Md.
Peter Buxbaum is a special contributor to Defense Systems.