Assessing the Thoroughness of an Organization’s Estimating Guidance

As GAO has previously reported, a lack of formal cost estimating guidance at agencies has led, in certain circumstances, to cost estimates of poor quality. This guidance serves as a mechanism for providing a standard cost-estimating process to agency officials and contractors. Cost estimating guidance also establishes roles and responsibilities for those preparing, reviewing, and updating all types of cost estimates. The 12-step cost estimating process and the process task lists that follow each chapter in this Guide can be used by agencies and other organizations to ensure that their cost estimating guidance, policies, and directives fully reflect industry and government standards for high-quality cost estimating. Table 17 summarizes the 12 steps and their associated tasks.

Table 17: The Twelve Steps and their Associated Tasks
Step Process Task
  1. Define the estimate’s purpose
  • Clearly define the estimate’s purpose.
  • Determine the estimate’s overall scope.
  • Determine the required level of detail for the estimate, which should be consistent with the level of detail available for the program.
  1. Develop the estimating plan
  • Ensure the cost estimating team’s composition is commensurate with the assignment.
  • Develop a written study plan that describes the cost estimating approach and includes a schedule to complete the cost estimate.
  • Ensure the team has access to the necessary subject matter experts.
  • Ensure the team has adequate time to develop a high-quality estimate, including the time needed to conduct site visits and collect data.
  1. Define the program
In a technical baseline document or group of documents, identify:
  • The program’s purpose and its system and performance characteristics;
  • All system configurations;
  • Any technology implications;
  • The program acquisition schedule and acquisition strategy;
  • The relationship to other existing systems, including predecessor or similar legacy systems;
  • Support (e.g., manpower, training) and risk items;
  • System quantities for development, test, and production; and
  • Deployment and maintenance plans.
  1. Determine the estimating structure
  • Define a work breakdown structure (WBS) that is standardized and product-oriented.
  • Ensure the cost estimate WBS matches the schedule and earned value management WBS, if applicable.
  • Describe each WBS element in a WBS dictionary.
  • Update the WBS as the program becomes better defined to reflect changes as they occur.
  1. Identify ground rules and assumptions
  • Document all cost-influencing ground rules and assumptions.
  • Document the rationale and historical data that support the ground rules and assumptions.
  • Include input from the technical community when developing ground rules and assumptions.
  • Document risks associated with assumptions and trace to specific WBS elements.
  1. Obtain the data
  • Create a data collection plan with emphasis on collecting current and relevant technical, programmatic, cost, and risk data.
  • Investigate possible data sources.
  • Collect data and normalize them for cost accounting, inflation, and quantity adjustments.
  • Analyze the data for cost drivers, trends, and outliers and compare results against rules of thumb and standard factors derived from historical data.
  • Interview data sources and document all pertinent information, including an assessment of data reliability and accuracy.
  • Store data for future estimates.
  1. Develop the point estimate
  • Develop the cost model, estimating each WBS element, using the best methodology from the data collected and including all estimating assumptions.
  • Express costs in constant year dollars.
  • Time-phase the results by spreading costs in the years they are expected to occur, based on the program schedule.
  • Sum the WBS elements to develop the overall point estimate.
  • Validate the estimate by looking for errors like double counting and omitted costs.
  • Compare estimate against the independent cost estimate and examine where and why there are differences.
  • Perform cross-checks on cost drivers to see if results are similar.
  • Update the model as more data become available or as changes occur and compare results against previous estimates.
  1. Conduct sensitivity analysis
  • Identify assumptions and parameters, including key cost drivers, as factors for sensitivity testing.
  • Test the sensitivity of cost elements to changes in identified factors.
  • Document the results, including those factors that are most sensitive to change.
  1. Conduct risk and uncertainty analysis
Conduct a risk and uncertainty analysis that includes the following steps:
  • Model probability distributions based on data availability, reliability, and variability.
  • Account for correlation between cost elements.
  • Use a Monte Carlo simulation model (or other modeling technique) to develop a distribution of total possible costs and an S-curve showing alternative cost estimate probabilities.
  • Identify the cumulative probability associated with the point estimate.
  • Identify contingency for achieving the desired confidence level.
  • Allocate the risk-adjusted cost estimate to WBS elements, if necessary.
  • Phase and convert the risk-adjusted estimate into budget year dollars.
  • Perform a risk and uncertainty analysis periodically as the cost estimate is updated to reflect progress and changes to risks.
  1. Document the estimate
  • Document all steps performed to develop the estimate so that a cost analyst unfamiliar with the program can recreate it quickly and produce the same result.
  • Document the purpose of the estimate, the team that prepared it, and who approved the estimate and on what date.
  • Describe the program, its schedule, and the technical baseline used to create the estimate.
  • Present the program’s time-phased life cycle cost.
  • Discuss all ground rules and assumptions.
  • Include auditable and traceable data sources for each cost element and document how the source data were normalized.
  • Describe in detail the estimating methodology and rationale used to derive each WBS element’s cost.
  • Describe the results of the risk, uncertainty, and sensitivity analyses and whether any contingency was identified.
  • Document how the estimate compares to the funding profile.
  • Track how the current estimate compares to previous estimates.
  1. Present the estimate to management for approval
  • Present the documented life cycle cost estimate to management.
  • Request acceptance of the estimate from management.
  • Act on and document feedback.
  1. Update the estimate to reflect actual costs and changes
  • Update the estimate to reflect changes in technical or program assumptions and keep it current as the program passes through new phases or milestones.
  • Replace estimates with EVM, EAC, and independent EACs from the integrated EVM system, if applicable.
  • Report progress on meeting cost and schedule estimates.
  • Perform a post mortem and document lessons learned for elements whose actual costs or schedules differ from the estimate.
  • Document changes to the program and how they affect the cost estimate.
Source: GAO. | GAO-20-195G

Case study 22 provides an example of the extent to which an agency’s cost estimating guidance incorporates best practices.

Case Study 22: Incomplete Cost Estimating Guidance, from Project and Program Management, GAO-15-29

The National Nuclear Security Administration (NNSA)—a semiautonomous agency within the Department of Energy (DOE)—is responsible for managing the nation’s nuclear security missions. These missions include maintaining the safety, security, and effectiveness of the U.S. nuclear weapons stockpile and reducing the threat posed by nuclear proliferation. To examine the extent to which DOE and NNSA cost estimating requirements and guidance for its projects and programs reflect best practices for developing and reviewing cost estimates, GAO reviewed DOE and NNSA requirements and guidance related to cost estimating for projects and programs and compared them with the best practices identified in our 2009 Cost Estimating and Assessment Guide.

DOE and NNSA cost estimating requirements and guidance for projects generally did not reflect best practices for developing cost estimates. DOE’s 2010 project management order required the use of only one of the 12 cost estimating best practice steps. Specifically, the order required an ICE be prepared at critical decision point 2 (approve project performance baseline) and critical decision point 3 (approve start of construction) for projects with an estimated cost of $100 million or greater. However, the order did not require any of the other 11 best practice steps, such as conducting a risk and uncertainty analysis, identifying ground rules and assumptions, documenting the estimate, developing a point estimate, or determining the estimating structure. According to the DOE officials responsible for developing DOE’s project management order, DOE had chosen to not require all cost estimating best practices in the order and instead included suggested approaches for developing cost estimates in the DOE cost estimating guide that accompanied the order. However, because neither DOE nor NNSA required the use of most cost estimating best practices for its projects, it was unlikely that NNSA and its contractors would consistently develop reliable cost estimates.

GAO recommended that, to enhance NNSA’s ability to develop reliable cost estimates for its projects and for its programs that have project-like characteristics, the Secretary of Energy DOE, among other things: (1) revise DOE’s project management order to require that DOE, NNSA, and its contractors develop cost estimates in accordance with the 12 cost estimating best practices, and (2) revise DOE’s cost estimating guide so that it fully reflects the 12 cost estimating best practices. In June 2015, based in part upon GAO’s work, the Secretary of Energy issued a memo to enhance and clarify departmental policy related to project management. The memo outlined changes that recent GAO reports had noted as areas for improvement. Specifically, the memo required that the DOE project management order, the cost estimating guide, and the Department of Energy Acquisition Regulations be revised consistent with the cost estimating best practices. The memo further specified that these and other provisions of the memo were to be made effective immediately and implemented as required project management procedures. This action satisfied this recommendation.