Welcome to our new site version. Your web page bookmarks may have changed, please search for pages by title to update them. Having problems ? Please try clearing your web browser cache and hard-reloading your web page first before contacting our webmaster.

Top Eleven Ways to Manage Technical Risk

[document] Submitted on 25 March, 2017 - 20:13
Keywords managing technical risk risk management

What is the Relationship Between “Approach” and Technical Risk?

The choice of an approach for man aging program technical risk should be made as soon as possible. DoDD 5000.1 mandates that the Program Manager (PM) develop a risk management approach “before decision authorities can authorize a program to
proceed into the next phase of the acquisition process.” All aspects of a risk management program are, in turn, determined by the approach selected. Delaying selection of a specific approach for managing technical risk will cause a program to flounder, especially if the contractor and the Government are following two different approaches. Further, the Integrated Product Team (IPT) cannot function successfully unless all members of the team – contractor and Government alike – are
using a common approach.

Although the Defense Acquisition Deskbook offers the PM several approaches to risk management covering a broad spectrum of program risks, only three approaches have been selected for inclusion in this publication. Why? Results of a 1997 survey of risk management in 41 Department of the Navy (DoN) programs revealed that the following three approaches to managing program technical risk represent those used almost exclusively by DoN PMs.

1. Critical Process: Technical risk management conducted primarily by assessing contractor critical design, test, and production processes against industry best practices and metrics, with the degree of variance determining the level of risk. These critical processes are generally not tailored for individual Work Breakdown Structure (WBS) elements.

2. Product (Work Breakdown Structure): Technical risk management based on individual product or WBS elements, with risk assessments based on deviations from a cost and schedule baseline. Risk is expressed as a “probability estimate”
rather than as a degree of process variance from a best practice.

3. Integrated Process/Product (WBS): Technical risk management based on specific critical processes affecting individual WBS elements. These critical design, test, and production processes are assessed against industry best practices and metrics, with the degree of variance determining the level of risk. These approaches are described in the remainder of this chapter.

Metadata
Version
NAVSO P-3686
Date published
1998-10
Language of Attachment(s)
English
Document type
manager's guide
Pages
147
Replaced/Superseded by document(s)
Cancelled by
Amended by
File MIME type Size (KB) Language Download
Top 11 Ways to Manage Technical Risk.pdf application/pdf   755.73 KB English DOWNLOAD!
File attachments
Cover images
Organisation(s)
Defines standard
Visit also