Skip Ribbon Commands
Skip to main content
 
      

Risk Management

The Program Manager is responsible for implementing effective risk management within program constraints. Successful risk management requires planning and resourcing, and should be implemented early in the life cycle beginning with the Materiel Solution Analysis (MSA) phase or earlier based on early collaboration among the operational, acquisition, and technology communities. The goal is to identify risks to inform decisions on structure and content, and develop mitigation strategies for the risks that must be addressed to deliver intended capabilities.

The practice of risk management constitutes a significant aspect of program management and draws from all disciplines, including systems engineering, use of models and simulation, requirements definition, developmental and operational test, earned value management (EVM), production planning, quality assurance, and logistics. Risk management needs to be both top-down (program leadership) and bottom-up (from working-level staff members) to be successful. PMs should encourage everyone on their program to take ownership of the risk management program and should be careful not to cultivate a “shoot the messenger” culture. All personnel should be encouraged to identify risks, issues, and opportunities and, as appropriate, to support analysis, mitigation, and monitoring activities.

Making risk management work depends on process, but more importantly on people with knowledge and experience in the disciplines relevant to the product, and with the resolve to identify and address the risks that could influence program objectives. An organizational climate, open to external perspectives, that seeks independent board members for design reviews can strengthen the effectiveness of a program’s risk management. Well-understood requirements flowed to the product, an integrated schedule coupled to earned value management (EVM), an independent cost estimate, and the tenacity to pull on the threads that reveal problems all contribute to prospects for success.

Making risk management work depends on process, but more importantly on people with knowledge and experience in the disciplines relevant to the product, and with the resolve to identify and address the risks that could influence program objectives. An organizational climate, open to external perspectives, that seeks independent board members for design reviews can strengthen the effectiveness of a program’s risk management. Well-understood requirements flowed to the product, an integrated schedule coupled to earned value management (EVM), an independent cost estimate, and the tenacity to pull on the threads that reveal problems all contribute to prospects for success.

Programs should define, implement, and document an appropriate, tailored risk process. The process should address planning, identification, analysis, mitigation, and monitoring of risks and issues.

  
  
  
  
  
GIDEP Requirements Guide Apr2008.pdf
  
Reference2/16/2016 6:26 PM
Robust Design and Taguchi Methods.pdf
  
Reference2/16/2016 6:03 PM
TPM EV and Risk Management.pdf
  
Reference9/24/2015 1:54 PM
ASN RDA website.aspx
  
Reference8/24/2015 3:12 PM
Example Risk Sources 723261.doc
  
Reference7/9/2015 6:47 PM
Evolutionary Acquisition - Seven Ways to Know If You Are Placing Your Program at Unnecessary Risk.aspx
  
Lessons Learned3/11/2015 8:32 PM
Risk Data Based on CMM.pdf
  
Presentation3/11/2015 8:32 PM
SpaceShuttle 1994 Tile Risk Analysis.pdf
  
Example3/10/2015 8:09 PM
113 Shepherd Booz Allen Brief for ASN RDA PM Risk Seminar.ppt
  
Presentation3/10/2015 8:09 PM
112 Szutenbach Seminar Risk for 9 May02 .ppt
  
Presentation3/10/2015 8:09 PM
Guidelines for Good RM towards IT projects.aspx
  
Lessons Learned3/10/2015 8:09 PM
cvn 77 risk management plan rev a.pdf
  
Example2/11/2015 6:58 PM
RISK Questionnaire.doc
  
Reference2/6/2015 2:50 PM
106 Advanced Schedule RiskPresentation Lisbon.ppt
  
Presentation3/28/2014 6:53 PM
Chat with DAU Assistant
Bot Image