Sec. 205. Capstone requirements
500 words·~2 min read·
/bill/118/s/5618/is/section-205·A research copy — for the controlling text, always check the official state or federal source. Not legal advice.
Chapter 221 of title 10, United States Code, is amended by adding at the end the following new section: The Secretary of each military department and the Director of one more defense agencies designated by the Secretary of Defense for purposes of this section shall establish a capstone requirement approach for each portfolio acquisition executive for which that official has responsibility to enable greater speed, agility, and innovation in fielding military capabilities. Each such capstone requirement shall be established in consultation with the Joint Requirements and Programming Board.
Under the capstone requirements for an acquisition portfolio, the Secretary of the military department, or Director of the defense agency shall— develop a general set of requirements for the acquisition portfolio in accordance with subsection
(c)under which programs or projects may be initiated; authorize the portfolio acquisition executive or similar portfolio manager for the portfolio to change the scope and requirements for programs within the portfolio, subject to subsection (d); assign representatives of operational forces to the acquisition portfolio and authorize them to perform the functions specified in subsection (e); maximize the use of prototyping, experimentation, and minimum viable products to shape capability scope and requirements; authorize the portfolio acquisition executive or similar portfolio manager to resource and acquire commercial or nondevelopmental items under the capstone requirement by validating the need with the representatives assigned under paragraph (3); manage information technology requirements using dynamically prioritized lists of user needs rather than large static requirements documents; and iteratively define, prioritize, and refine requirements at the portfolio, program, and iteration levels based on user input and previous deliveries. The capstone set of requirements for an acquisition portfolio developed under subsection (b)(1) shall be designed— to guide the iterative delivery of an integrated suite of capabilities to maximize operational impact; to provide enduring themes based on strategic needs and relevant concepts of operation, not system-specific; to include measures of force effectiveness for a force mix of capabilities to be measured against; and to include kill chains, effects chains, vignettes of operational scenarios, and related mission engineering initiatives across the Department of Defense. The authority under subsection (b)(2)— shall be carried out in consultation with operational commands and the Joint Requirements and Programming Board; and does not include authority to change key performance parameters for a major defense acquisition program. An operational representative assigned to an acquisition portfolio under subsection (b)(3) shall be provided authority— to shape the vision and priorities for key capability areas; to provide the acquisition community and developers insights into operations; to provide feedback on interim developments; to validate the need for commercial or nondevelopmental items; to foster collaboration among the acquisition community, developers, and users of the capability to be fielded; and to provide advice to the portfolio acquisition executive or similar portfolio manager. . The table of sections at the beginning of chapter 221 of title 10, United States Code, is amended by inserting after the item relating to section 3208 the following new item: 3209. Capstone requirements. .