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

There shall be an acquisition strategy for each major defense acquisition program and each major system approved by a decision authority. the content of the strategy; and the review and approval process for the strategy. the strategy clearly describes the proposed business case and capability management approach for the program or system, and to the maximum extent practicable, describes how capability requirements will be met through delivery of such program or system; the strategy contains a clear explanation of the resources, such as time, funding, and management capacity, necessary to meet capability requirements; the strategy is tailored to address program requirements and constraints; and the strategy considers the items listed in paragraph (2). An approach that delivers required capabilities in increments, each depending on available mature technology, and that recognizes up front the need for future capability improvements or transitions to alternative end items through use of continuous competition. Requirements related to logistics, maintenance, and sustainment in accordance with sections 2464 and 2466 of this title, and the acquisition of technical data, computer software, and associated licenses, to enable such requirements in accordance with sections 3771 through 3775 of this title. A process for collaborative interaction and market research with the science and technology community, including Department of Defense science and technology reinvention laboratories, government innovation cells, academia, small businesses, nontraditional defense contractors, and other contractors. Identification of enterprise-wide designs and standards in support of an architecture that provides for an integrated suite of capabilities that focuses on simplicity of implementation and speed of delivery. Overarching roadmaps that create integrated strategic schedules of legacy systems and new capabilities. A contracting strategy that develops long-term partnerships with multiple companies to actively contribute to architectures, development, production, and sustainment across the capabilities to be developed by decomposing large systems into smaller sets of projects across time and technical component. An assignment of roles and responsibilities of key personnel of the acquisition workforce, identification of external stakeholder dependencies, and the need for subject matter expert inputs at critical points in the program, including the need for special hiring authority or advisory and assistance services, in order to deliver the desired capabilities. A process of testing and experimentation with the test community and end users to ensure continuous user feedback, acceptance, and development of concepts of operations. The decision authority shall review and approve, as appropriate, the acquisition strategy for a major defense acquisition program or major system prior to the acquisition decision memorandum and ensure that the strategy is updated at regular intervals to incorporate significant changes to program requirements, resourcing, or acquisition decisions. In this section, the term “decision authority”, with respect to a major defense acquisition program or major system, means the official within the Department of Defense designated with the overall responsibility and authority for acquisition decisions for the program or system, including authority to approve entry of the program or system into the next phase of the acquisition process.