10 U.S.C. § 4211 — Acquisition strategy

(a) Acquisition^* strategy required. Each major defense acquisition program^* and each major system^* approved by a decision authority must have an acquisition strategy.

(b) Responsible official. For each strategy, the Under Secretary of Defense for Acquisition and Sustainment is responsible for issuing and maintaining requirements for (1) its contents and (2) its review and approval process. The decision authority has that responsibility instead when the decision authority is the service acquisition executive^* of the military department managing the program.

(c) Considerations. (1) The responsible official must ensure that the strategy (A) clearly describes the proposed business case and capability-management approach and, as far as practicable, how delivery will meet capability requirements; (B) clearly explains needed time, funding, management capacity, and other resources; (C) is tailored to the program’s requirements and limits; and (D) considers paragraph (2). (2) When appropriate, each strategy must consider: (A) delivering capabilities in increments using mature technology, while recognizing future improvements or transitions through continuous competition; (B) logistics, maintenance, sustainment, and acquisition of technical data, software, and licenses needed for them; (C) collaboration and market research with science and technology organizations, laboratories, innovation cells, schools, small businesses, nontraditional defense contractors, and other contractors; (D) enterprise-wide designs and standards supporting an integrated, simple, fast-to-deliver architecture; (E) roadmaps integrating schedules for existing systems and new capabilities; (F) contracts creating long-term partnerships with multiple companies for architecture, development, production, and sustainment by breaking large systems into smaller projects over time and technical components; (G) roles for key acquisition personnel, outside dependencies, and expert input at critical points, including any need for special hiring or advisory services; and (H) testing and experimentation with testers and end users for continuing feedback, acceptance, and development of operating concepts.

(d) Review. Before the acquisition decision memorandum, the decision authority must review and, as appropriate, approve the strategy. The authority must ensure regular updates that reflect significant changes in requirements, resources, or acquisition decisions.

(e) Decision authority defined. Here, “decision authority” means the Department of Defense official given overall responsibility and authority for acquisition decisions for the program or system, including authority to approve its entry into the next acquisition phase.