Risk Management Guide for DoD Acquisition
DAU. 2006. Risk Management Guide for DoD Acquisition. Sixth Edition, Version 1. Ft. Belvoir, VA, USA: Defense Acquisition University (DAU)/U.S. Department of Defense.
Annotation
Risk Management
The Risk Management Guide for DoD Acquisition provides risk management guidance for the program management practitioner and is the product of an effort led by OUSD(AT&L) Systems and Software Engineering, Enterprise Development (OUSD(AT&L) SSE/ED), and acquisition management organizations throughout DoD, to include DAU. The updated Guide reflects lessons learned on the application of risk management on past programs. This guide has been structured to provide a basic understanding of risk management concepts and processes. It offers clear descriptions and concise explanations of core steps to assist in managing risks in acquisition programs. Its focuses on risk mitigation planning and implementation rather on risk avoidance, transfer, or assumption.
The Sixth Edition of the Guide places additional emphasis on the role and management of future root causes. Each risk event has three components:: 1) a future root cause; 2) the probability of the future root cause occurring; and 3) the consequence / impact if the root cause occurs.
SEBoK Discussion
Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.
If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.
blog comments powered by Disqus