TEMPLATES ARE BASED ON TASK FORCE EXPERIENCE
The templates were initiated using the reports of the five
panels that made up the DSB task force. The total set of recommended
initiatives and principles were tested against their relationship to
"technical risk," using the background and knowledge of the members of the
task force as the basis for defining these technical risks and for setting out
methods for minimizing them during the transition from development to
production. From the results, a set of templates was developed for use in
describing low risk programs. A low risk program is a program that is not
likely to give trouble during the transition out of development.
Each template describes an area of risk and then specifies technical methods for reducing that risk. The templates themselves are nominally two-or three-page documents that usually describe a technical problem that in turn creates a high risk program. The templates then describe a readily available technical solution to the problem based on the lessons learned from analysis of a substantial number of programs.
Justification for the use is then provided along with supporting data.
Throughout this document there are timelines for many template activities that begin and/or end between two major milestones. In such cases, the timeline is depicted for simplicity purposes as beginning and/or ending in the middle of the program phase. It is left to the users of this document to determine how early or how late in the phase Ď the template activity begins or ends; and such a determination will be influenced by the types of program, the acquisition plan, and the best judgment of experienced Government and industry personnel.
The subsequent pages of this document contain all the templates generated by the DSB task force to reduce risk inherent in the design, test, and production processes. Additional templates have been generated as a result of a DoD and industry wide review. Since some risk is associated with funding, facilities, management issues, and the transition plan for design, test, and production, the entire network of templates is arranged in a sequence considered logical from a typical program managerís viewpoint. Funding is presented prominently because it influences every other template in the transition document. The total network of critical path templates is shown in figure 1-2*.