Professional Documents
Culture Documents
Is Weapon System Cost Growth Increasing. Risk is Cost Estimating, General Cost Estimating Requirements to Support
A quantitative Assessment of Completed introduction & the BMDO Approach to Risk. New Congressional Reporting
and Ongoing Programs. RAND Project Air Coleman, Summervile, DuBois, Myers. Requirements. Coonce, Rutkowski, Hunt.
Force, 2007 DoDCAS. 2000. NASA PM Challenge, 2008.
For any input or method utilized in your estimate you should think about
the associated uncertainty
Unit III - Module 9
2003 SCEA. All rights reserved.
8
Definitions
Risk analysis terms are used in many different fields,
but often with different meanings - The following
definitions will create a terminology specific to risk
analysis
Risk in Finance
Risk is the variability of returns from an investment1
In finance, risk refers to variance
Risk in Cost
The probability of loss due to cost overrun
In cost, risk refers to the mean
Variance is described as uncertainty
1 Wall Street Words: An A to Z Guide to Investment Terms for Todays Investor. Scott, David. 1993
2 BusinessDictionary.com
1 BusinessDictionary.com
100%
90%
80%
Cum Probability
70%
60%
50% CV=.35
40%
30%
20%
10%
0%
0 25 50 75 100 125 150 175 200
Cost
Beta 0.40
Fitted Normal
Solves negative cost and duration issues
0.35
0.30
Fitted Lognormal
0.25
Skewed 0.00
0.0 5.0 10.0 15.0 20.0 25.0
Subjective Distribution
Uncertainty modeled as triangular distribution
0.5
0.4
0.3
0.2
0.1
0
9 10 11 12 13 14 15 16 17 18 19 20
Weight
Always try the statistical approach first and validate with Program
Engineer input
Unit III - Module 9
2003 SCEA. All rights reserved.
25
Step 2: Assess the Uncertainty in Cost
Estimating Methodology
14
12
10 Cost
Point Estimate
8 Min Weight
Cost
6 Likely Weight
Max Weight
4
Linear (Cost)
2
0
0 2 4 6 8 10 12 14 16 18
Weight
Hopefully you have already started thinking about ways you can apply
these techniques to your current estimate
Unit III - Module 9
2003 SCEA. All rights reserved.
31
Discrete Risks & Opportunities
These are events that, if they occur, will impact cost
and/or schedule
This step should be integrated with the risk
management effort
Risks collected by the risk management team should be
incorporated into the risk analysis
These risks should be tracked throughout the lifetime of the
program and used to update the program estimate
Results from the risk analysis should be used to aid in the
choosing of risk mitigation plans
Oftentimes, once the estimate is complete, risks and
opportunities are forgotten until next estimate revision
Risks and opportunities uncovered within the risk analysis
should be incorporated with the risk management effort
Adapted from: Making Risk Management Tools More Credible: Calibrating the Risk Cube. Coleman, Richard; Summerville,
Jessica; Dameron, Megan. SCEA Conference. June 2006. Washington DC
Unit III - Module 9
2003 SCEA. All rights reserved.
32
Collecting Risks & Opportunities
Risks & Opportunities are generally collected through
interviews with engineers and the program
management team
When interviewing, try evoking risks using an if-then
statement
Example: If the instrument doesnt pass environmental testing
then a hardware re-spin will be required
Beware of double counting when capturing risks and
opportunities
Risks typical to similar programs are contained in the data
used to generate the CERs or technology uncertainties (e.g.
weight growth)
To avoid double counting try to focus on risks that are specific
to the program that is the subject of the risk analysis
Unit III - Module 9
2003 SCEA. All rights reserved.
33
Convert Risk Scoring to Pf and Cf
The next step is to determine quantitative measures
for Likelihood and Consequence
Probability is somewhat easier to define than
consequence (i.e. 0% Pf to 100% Pf)
Consequence levels may take on different meanings
when scoring
5 1, 4
Likelihood
3 3
1 2
1 2 3 4 5
Consequence
12%
10% 0
0.1
0.2
8%
0.3
0.4
CV
6% 0.5
0.6
0.7
4%
0.8
0.9
2% 1
0%
0 10 20 30 40 50 60 70 80 90 100
Number of Distributions
SEPM
300 300
250 250
200 200
1000 1200 1400 1600 1800 2000 1000 1200 1400 1600 1800 2000
Recurring Production Recurring Production
r: .50
r: 0 r: 1
80%
confidence level it is at 70%
20% PE
programs 10%
0%
0 2 4 6 8 10 12 14 16 18 20
Cost
Likelihood Consequence
Level Likelihood Level Technical Schedule Cost
Minimal or no Minimal or
1 Minimal or no impact Note: Generic Risk Cube
impact no impact
1 Not Likely
Minor technical < (1% of
2
Consequence
Slip < * month(s)
shortfall Budget)
Low
2 5
Likelihood Moderate
Slip < * month(s) of
critical path. < (5% of
3 technical
Sub-system slip > * Budget)
shortfall
Likelihood
3 Likely month(s). 4
Unacceptable,
< (10% of 3
4 workarounds Slip < * months
4 Highly Likely available
Budget)
Unacceptable, 2
Near Cannot achieve key > (10% of
5 5 no alternative
program milestones
Certainty exist
Budget)
1
1 2 3 4 5
Consequence
Category Level Likelihood
Category Level Likelihood Consequence
Risk Item Statement
Statement
Assessments: Cause
Mitigation
Comments
Mitigation
Once the model is built, it can be quickly updated: low Requires data and sophisticated data analysis - High fixed cost
recurring cost to perform analysis to performing analysis
Inputs-Based
Simulation Relies on statistics and is the most objective of all three Can miss unknown-unknown risks
methods
Difficult to mesh probabilistic results with a deterministic world
Because performed at a lower level, is easiest to integrate with (example: allocating $'s to WBS items)
the IMS to perform schedule risk analysis
Is still a statistical method, just generally at a higher level Choice of uncertainty distributions is subjective and will
always be questioned
Applying historical, top level cost growth distributions
Outputs-Based captures unknown-unknown risks Difficult to mesh probabilistic results with a deterministic world
Simulation (example: allocating $'s to WBS items)
The protect scenario is invaluable for program managers and Confidence level of point estimate, CV of estimate and choice
provides a tangible and actionable set of risks to guard against of uncertainty distribution are all subjective. If the other two
Scenario Based methodologies are entirely centered around finding these three
Method measures, and we have studies showing that SME's tend to
underestimate uncertainty, what leads us to believe that we can
accurately estimate them correctly?
The above table assumes the analysis is performed correctly, it does not account for analyst errors