Tap any paragraph to write a margin note. Your notes collect in the Desk below the text and file under cases with @. The side-by-side margin rail opens on a larger screen.

Code · STATUTE-COMPILATIONS · National Defense Authorization Act for Fiscal Year 2018 · Sec. 873

Sec. 873. PILOT PROGRAM TO USE AGILE OR ITERATIVE DEVELOPMENT METHODS TO TAILOR MAJOR SOFTWARE-INTENSIVE WARFIGHTING SYSTEMS AND DEFENSE BUSINESS SYSTEMS

958 words·~4 min read·/statute-compilations/comps-13932/sec-873

A research copy — for the controlling text, always check the official state or federal source. Not legal advice.

## SEC. 873 PILOT PROGRAM TO USE AGILE OR ITERATIVE DEVELOPMENT METHODS TO TAILOR MAJOR SOFTWARE-INTENSIVE WARFIGHTING SYSTEMS AND DEFENSE BUSINESS SYSTEMS **[**[10 U.S.C. 2223a note](/us/usc/t10/s2223a)**]** ###
(a)Pilot Program ####
(1)In general Not later than 30 days after the date of the enactment of this Act, the Secretary of Defense, in consultation with the Secretaries of the military departments and the chiefs of the armed forces, shall establish a pilot program to tailor and simplify software development requirements and methods for major software-intensive warfighting systems and defense business systems. ####
(2)Implementation plan for pilot program Not later than 120 days after the date of the enactment of this Act, the Secretary of Defense, in consultation with the Secretaries of the military departments and the chiefs of the armed forces, shall develop a plan for implementing the pilot program required under this subsection, including guidance for implementing the program and for selecting systems for participation in the program. ####
(3)Selection of systems for pilot program #####
(A)The implementation plan shall require that systems be selected as follows: ######
(i)For major software-intensive warfighting systems, one system per armed force and one defense-wide system, including at least one major defense acquisition program or major automated information system. ######
(ii)For defense business systems, not fewer than two systems and not greater than eight systems. #####
(B)In selecting systems or subsystems for participation, the Secretary shall prioritize systems as follows: ######
(i)For major software-intensive warfighting systems, systems that— ######
(I)have identified software development as a high risk; ######
(II)have experienced cost growth and schedule delay; or ######
(III)did not deliver any operational capability within the prior calendar year. ######
(ii)For defense business systems, systems that— ######
(I)have experienced cost growth and schedule delay; ######
(II)did not deliver any operational capability within the prior calendar year; or ######
(III)are underperforming other systems within a defense business system portfolio with similar user requirements. ###
(b)Realignment Plans ####
(1)In general Not later than 60 days after selecting a system for the pilot program under subsection (a)(3), the Secretary shall develop a plan for realigning the system by breaking down the system into smaller increments using agile or iterative development methods. The realignment plan shall include a revised cost estimate that is lower than the cost estimate for the system that was current as of the date of the enactment of this Act. ####
(2)Realignment execution Each increment for a realigned system shall— #####
(A)be designed to deliver a meaningfully useful capability within the first 180 days following realignment; #####
(B)be designed to deliver subsequent meaningfully useful capabilities in time periods of less than 180 days; #####
(C)incorporate multidisciplinary teams focused on software production that prioritize user needs and control of total cost of ownership; #####
(D)be staffed with highly qualified technically trained staff and personnel with management and business process expertise in leadership positions to support requirements modification, acquisition strategy, and program decisionmaking; #####
(E)ensure that the acquisition strategy for the realigned system is broad enough to allow for proposals of a service, system, modified business practice, configuration of personnel, or combination thereof for implementing the strategy; #####
(F)include periodic engagement with the user community, as well as representation by the user community in program management and software production activity; #####
(G)ensure that the acquisition strategy for the realigned system favors outcomes-based requirements definition and capability as a service, including the establishment of technical evaluation criteria as outcomes to be used to negotiate service-level agreements with vendors; and #####
(H)consider options for termination of the relationship with any vendor unable or unwilling to offer terms that meet the requirements of this section. ###
(c)Removal of Systems The Secretary may remove a system selected for the pilot program under subsection (a)(3) only after the Secretary submits to the Committees on Armed Services of the Senate and House of Representatives a written determination that indicates that the selected system has been unsuccessful in reducing cost or schedule growth, or is not meeting the overall needs of the pilot program. ###
(d)Education and Training in Agile or Iterative Development Methods ####
(1)Training requirement The Secretary shall ensure that any personnel from the relevant organizations in each of the military departments and Defense Agencies participating in the pilot program, including organizations responsible for engineering, budgeting, contracting, test and evaluation, requirements validation, and certification and accreditation, receive targeted training in agile or iterative development methods, including the interim course required by section 891 of this Act. ####
(2)Support In carrying out the pilot program under subsection (a), the Secretary shall ensure that personnel participating in the program provide feedback to inform the development of education and training curricula as required by section 891. ###
(e)Sunset The pilot program required under subsection
(a)shall terminate on September 30, 2023. Any system selected under subsection (a)(3) for the pilot program shall continue after that date through the execution of its realignment plan. ###
(f)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. **[**Section 874 was repealed by section 811(b)(6)(B) of division A of Public Law 119-60.**]**
Connectionstraces to 1
Traces to 1 document
1 reference not yet in our index
  • Pub. L. 119-60
Citation graph
cites case law
Sec. 873
PILOT PROGRAM TO USE AGILE OR ITERATIVE DEVELOPMENT METHODS TO TAILOR MAJOR SOFTWARE-INTENSIVE WARFIGHTING SYSTEMS AND DEFENSE BUSINESS SYSTEMS
Pub. L.Pub. L. 119-60
Cites 2Cited by 0 across 0 sources
★   the supreme law of the land   ★
Don't Tread on Me
E Pluribus Unum — out of many, one

"If you don't know your rights, you don't have any."

Marginalia · a citizen's law index
A research desk, not legal advice. Always read the cited source before relying on a summary.
Questions or an issue? support@self-law.org
disclaimerMarginalia is a research index, not a law firm. Nothing on this site is legal, tax, or financial advice and no attorney–client relationship is formed by using it. Statutes, regulations, and case law change; summaries, search results, AI output, and member posts may be incomplete, out of date, or wrong. Any interpretation drawn from material on this site should be validated by a licensed attorney in your jurisdiction before you act on it.