Sec. 1626. Evaluation of agile acquisition of cyber tools and applications
554 words·~3 min read·
/bill/115/hr/2810/eas/section-1626A research copy — for the controlling text, always check the official state or federal source. Not legal advice.
The Commander of the United States Cyber Command 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 Forces Cyber Command, and the Marine Corps Cyberspace Command. The goal of the evaluation required by subsection
(a)is to identify a set of practices that will— increase the speed of development of cyber capabilities of the Armed Forces; provide more effective tools and capabilities for developing, acquiring, and maintaining cyber tools and applications; and create a repeatable, disciplined process for developing, acquiring, and maintaining cyber tools and applications whereby progress and success or failure can be continuously measured. The evaluation required by subsection
(a)shall include consideration of agile software development, agile acquisition, and such other similar best practices of commercial industry. In carrying out the evaluation required by subsection (a), the Commander shall assess requirements for implementing the practices described in paragraph (1), consider changes that would be necessary to established acquisition practices, including the following: The requirements process. Contracting. Testing. User involvement in the development process. Program management. Milestone reviews and approvals. The definitions of research and development , procurement , and sustainment . The constraints of current appropriations account definitions. 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. In conducting the evaluation required by subsection (a), the Commander shall— obtain services and expertise from— the Defense Digital Service; and federally funded research and development centers, such as the Software Engineering Institute and the MITRE Corporation; and consult with such commercial software companies as the Commander considers appropriate to learn about commercial best practices. 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, including all aspects of implementation necessary for the success of the recommended methods. Not later than 14 days after submitting recommendations to the Secretary under paragraph (1), the Commander shall brief the congressional defense committees on the recommendations the Commander submitted under paragraph (1). 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 exercising of the acquisition authority of the Commander of United States Cyber Command under section 807 of the National Defense Authorization Act for Fiscal Year 2016 ( Public Law 114–92 ; 10 U.S.C. 2224 note). In this section: The term agile acquisition means acquisition pursuant to a methodology for delivering multiple, rapid, incremental capabilities to the user for operational use, evaluation, and feedback. The incremental development and fielding of capabilities, commonly called spirals , spins , or sprints , can be measured in a few weeks or months, and involve continuous participation and collaboration by users, testers, and requirements authorities. The term agile development means development pursuant to a set of software development methodologies based on iterative development, in which requirements and solutions evolve through collaboration between self-organizing cross-functional teams.
Connectionstraces to 2
Traces to 2 documents
Citation graph
cites case law
Sec. 1626
Evaluation of agile acquisition of cyber tools and applications
Cites 2Cited by 0 across 0 sources