2.0. Overview
This chapter discusses the development and management of program strategies (i.e., the Technology Development Strategy and the Acquisition Strategy (AS)) for Department of Defense acquisition programs. It addresses the information requirements that the Program Manager must consider in preparing the TDS and the AS, respectively.
2.0.1. Purpose
The purpose of this Chapter is to provide information and guidance needed to develop a Technology Development Strategy and to develop and maintain a program-level Acquisition Strategy. A program’s strategy should be developed organically by the Program Management Office in collaboration with related communities and stakeholders.
2.0.2. Content
Section 2.1 describes Program Strategies in the broad sense. Section 2.2 discusses Program Strategy Documentation Requirements; Section 2.3 discusses the relationship of the Program Strategy to other program documents; Section 2.4 discusses the relationship of the Program strategy to the Request for Proposal; Section 2.5 discusses Security Classification Markings for Program Strategies; Section 2.6 describes the Program Strategy approval process; and Section 2.7 is a high level summary of some fundamental differences between an acquisition plan and an Acquisition Strategy. Section 2.8 addresses the Technology Development Strategy/Acquisition Strategy outline.
2.1. Program Strategies—General
Program strategies include the Technology Development Strategy (TDS) and the Acquisition Strategy (AS).
Well-developed program strategies optimize the time and cost required to satisfy approved capability needs. Program strategies should be exploratory in nature. That is, they should express clearly the Program Manager’s approach to developing and/or procuring the material or service—from a business, contracting, and programmatic point of view. The focus of each strategy should be on the rationale for the approach, not solely a description of the source itself. The strategy should not be a repetition of statute, policy, or regulation. It should describe what actions are being taken—and to what end.
DAG Tutorial 
