Department of Defense INSTRUCTION

DoDI 5000.02, January 7, 2015
5. TECHNICAL RISK AND OPPORTUNITY MANAGEMENT. Technical risk management
should address risk identification, analysis, mitigation planning, mitigation implementation, and
tracking. Technical risks should be quantified and implications reflected in the program’s
Integrated Master Schedule and Integrated Master Plan. The Program Manager should also work
with the applicable science and technology communities and Component acquisition leadership
to influence technology investment planning. The goal is to both mitigate risks and create
opportunities for technology development outcomes that could have a positive impact on
meeting performance objectives as well as thresholds. Program risks, and opportunities as
applicable, will be assessed at technical reviews and will include specific cost and schedule
implications.
6. TECHNICAL PERFORMANCE MEASURES AND METRICS. The Program Manager will
use technical performance measures and metrics to assess program progress. Analysis of
technical performance measures and metrics, in terms of progress against established plans, will
provide insight into the technical progress and risk of a program.
7. TECHNICAL REVIEWS. Program Managers will:
a. Conduct technical reviews of program progress for systems in development as a basis for
transitioning between phases within the development plan of work. Reviews will be eventdriven
and based on the review entrance criteria as documented in the SEP.
b. Program Managers will plan for and conduct design reviews as needed to manage
program planning and execution. Design review planning will be included in the SEP. Any
program that is not initiated at Milestone C will include the following design reviews:
(1) PDR. The PDR assesses the maturity of the preliminary design supported by the
results of requirements trades, prototyping, and critical technology demonstrations. The PDR
will establish the allocated baseline and confirm that the system under review is ready to proceed
into detailed design (development of build-to drawings, software code-to documentation, and
other fabrication documentation) with acceptable risk. For MDAPs and MAIS programs, a
system-level PDR assessment will be conducted and provided to the MDA. For Acquisition
Category (ACAT) ID and ACAT IAM programs, DASD(SE) will conduct the PDR assessment
to inform the Milestone Decision Authority (MDA) of technical risks and the program’s
readiness to proceed into detailed design. The Program Manager will make the program
information needed for this assessment available and provide for DASD(SE) participation in the
program's PDR process. For ACAT IC and ACAT IAC programs, the Component Acquisition
Executive (CAE) will conduct the PDR assessment.
(2) Critical Design Review (CDR). The CDR assesses design maturity, design build-to
or code-to documentation, and remaining risks and establishes the initial product baseline. It will
be used as the decision point that the system design is ready to begin developmental prototype
hardware fabrication or software coding with acceptable risk. For MDAPs and MAIS programs,
a system-level CDR assessment will be conducted and the results will be provided to the MDA.
Change 2, 02/02/2017 96
ENCLOSURE 3