IBR Risks

Identifying potential program risk is one main goal of an IBR. Risks are generally categorized as cost, management process, resource, schedule, and technical (see table 47).

Program managers should also outline the criteria for evaluating risks in table 47 and develop a method for tracking them within the risk management process. All risks identified in the IBR should be monitored.

Table 47: Integrated Baseline Review Risk Categories

Scroll to the right to view full table.

Category	Definition
Cost	Evaluates whether the program can succeed within budget, resource, and schedule constraints as depicted in the performance measurement baseline. Cost risk is driven by the quality and reasonableness of the cost and schedule estimates, accuracy of assumptions, use of historical data, and whether the baseline covers all efforts outlined in the statement of work.
Management process	Evaluates how well management processes provide effective and integrated technical, schedule, cost planning, and baseline change control. It examines whether management processes are being implemented in accordance with the EVM system description. Management process risk is driven by the need for early view into risks, which can be hampered by the inability to establish and maintain valid, accurate, and timely performance data, including subcontractors’ data.
Resource	Represents risk associated with the availability of personnel, facilities, and equipment needed to perform program-specific tasks. Includes staff lacking because of other company priorities and unexpected downtime precluding or limiting the use of equipment or facilities when needed.
Schedule	Addresses whether all work scope has been captured in the schedule and time allocated to lower-level tasks meets the program schedule. Schedule risk is driven by the interdependency of scheduled activities and logic and the ability to identify and maintain the critical path.
Technical	Represents the reasonableness of the technical plan for achieving the program’s objectives and requirements. Deals with issues such as the availability of technology, capability of the software development team, and design maturity.

Source: Adapted from Department of Defense, Office of the Secretary of Defense (AT&L), The Program Manager’s Guide to the Integrated Baseline Review Process (Washington, D.C.: April 2003). | GAO-20-195G