Sec. 1642. EVALUATION OF AGILE OR ITERATIVE DEVELOPMENT OF CYBER TOOLS AND APPLICATIONS
701 words·~3 min read·
/statute-compilations/comps-13932/sec-1642A research copy — for the controlling text, always check the official state or federal source. Not legal advice.
## SEC. 1642 EVALUATION OF AGILE OR ITERATIVE DEVELOPMENT OF CYBER TOOLS AND APPLICATIONS ###
(a)Evaluation Required The Commander of the United States Cyber Command (in this section referred to as the “Commander”) shall conduct an evaluation of alternative methods for developing, acquiring, and maintaining software-based cyber tools and applications for the United States Cyber Command, the Army Cyber Command, the Fleet Cyber Command, the Air Force Cyber Command, and the Marine Corps Cyberspace Command. ###
(b)Goal The goal of the evaluation required by subsection
(a)shall be to identify a set of practices that will— ####
(1)increase the speed of development of cyber capabilities of the Armed Forces; ####
(2)provide more effective tools and capabilities for developing, acquiring, and maintaining software-based cyber tools and applications for the Armed Forces; and ####
(3)create a repeatable, disciplined process for developing, acquiring, and maintaining software-based cyber tools and applications for the Armed Forces through which progress and success or failure can be continuously measured. ###
(c)Consideration of Agile or Iterative Development, and Other Best Practices ####
(1)In general The evaluation required by subsection
(a)shall include, with respect to the development, acquisition, and maintenance of software-based cyber tools and applications, consideration of agile or iterative development practices, agile acquisition practices, and other similar best practices of commercial industry. ####
(2)Considerations In carrying out the evaluation required by subsection (a), the Commander shall assess requirements for implementing the practices described in paragraph
(1)and consider changes to established acquisition practices that may be necessary to implement the practices described in such paragraph, including changes to the following: #####
(A)The requirements process. #####
(B)Contracting. #####
(C)Testing. #####
(D)User involvement in the development process. #####
(E)Program management. #####
(F)Milestone reviews and approvals. #####
(G)The definitions of “research and development”, “procurement”, and “sustainment”. #####
(H)The constraints of current appropriations account definitions. ###
(d)Assessment of Training and Education Requirements In carrying out the evaluation required by subsection (a), the Commander shall assess training and education requirements for personnel in all areas and at all levels of management relevant to the successful adoption of new acquisition models and methods for developing, acquiring, and maintaining cyber tools and applications as described in such subsection. ###
(e)Services and Expertise In carrying out the evaluation required by subsection (a), the Commander shall— ####
(1)obtain services and expertise from— #####
(A)the Defense Digital Service; and #####
(B)federally funded research and development centers, such as the Software Engineering Institute and the MITRE Corporation; and ####
(2)consult with such commercial software companies as the Commander considers appropriate to learn about relevant commercial best practices. ###
(f)Recommendations ####
(1)In general Not later than 120 days after the date of the enactment of this Act, the Commander shall submit to the Secretary of Defense recommendations for experimenting with or adopting new acquisition methods identified pursuant to the evaluation under subsection (a), including recommendations for any actions that should be carried out to ensure the successful implementation of such methods. ####
(2)Congressional briefing Not later than 14 days after submitting recommendations to the Secretary under paragraph (1), the Commander shall provide to the congressional defense committees a briefing on the recommendations. ###
(g)Preservation of Existing Authority The evaluation required under subsection
(a)is intended to inform future acquisition approaches. Nothing in this section shall be construed to limit or impede the Commander in exercising the authority provided under section 807 of the National Defense Authorization Act for Fiscal Year 2016 (Public Law 114-92; 10 U.S.C. 2224 note). ###
(h)Agile or Iterative Development Defined In this section, the term “agile or iterative development”, with respect to software— ####
(1)means acquisition pursuant to a method for delivering multiple, rapid, incremental capabilities to the user for operational use, evaluation, and feedback not exclusively linked to any single, proprietary method or process; and ####
(2)involves— #####
(A)the incremental development and fielding of capabilities, commonly called “spirals”, “spins”, or “sprints”, which can be measured in a few weeks or months; and #####
(B)continuous participation and collaboration by users, testers, and requirements authorities.
Connectionstraces to 2
Traces to 2 documents
Citation graph
cites case law
Sec. 1642
EVALUATION OF AGILE OR ITERATIVE DEVELOPMENT OF CYBER TOOLS AND APPLICATIONS
Cites 2Cited by 0 across 0 sources