|
Page 14 of 22
5.1 WBS
The WBS encompasses the structure of everything that will be done or delivered
in a program. Therefore, assessing each and every element of the WBS will, in
most programs, assure overall closure of the risk assessment. Each WBS element
should be reviewed by each organizational element as noted above. This approach
is a beginning of concurrent engineering and assures that inter-functional,
inter-discipline and inter-specialty concerns are accommodated.
Specific attributes of the WBS that make it a valid basis for such reviews
are:
The WBS identifies in a structured form all elements of the program in each
phase, and provides a comprehensive framework for assessing each and every aspect
of the program for potential risks.
The specification trees map directly to the WBS which provides traceability
between performance requirements and risks for hardware and software items.
The WBS provides a direct exposition of the system hierarchy and interfaces
for purposes of identifying risk propagation.
The WBS can also provide a single point-of-contact for each risk through the
management structure, i.e., the individual responsible for the CWBS work package.
One problem with the WBS as a review tool is that care must be taken to assure
that all external influences on any elements are considered in the reviews.
Such influences include interfaces of any type (intra-program and external)
and such issues as GFE, special test equipment, etc. The specification and ICD
"trees" can provide a structure to assure interfaces are not neglected.
There is also the consideration that the WBS must be well formed or it becomes
a risk in itself and a shaky basis for reviewing risks. Problems with the WBS
should be reported on an element-by-element basis as an issue for consideration
as a risk. A typical problem is the lack of interface hardware elements when
such hardware is clearly need. Awkward WBS constructs can also create risks.
For example, some WBS structures are very difficult for purposes of subcontracting,
manufacturing scheduling, ICO for the prototypes, interface control, etc.
|
