Defense Acquisition University
Defense Acquisition University Structure.—
The Secretary of Defense, acting through the Under Secretary of Defense for Acquisition, Technology, and Logistics, shall establish and maintain a defense acquisition university structure to provide for—
the professional educational development and training of the acquisition workforce; and
research and analysis of defense acquisition policy issues from an academic perspective.
Civilian Faculty Members.—
The Secretary of Defense may employ as many civilians as professors, instructors, and lecturers in the defense acquisition university structure as the Secretary considers necessary.
The compensation of persons employed under this subsection shall be as prescribed by the Secretary.
In this subsection, the term “defense acquisition university” includes the Defense Systems Management College.
Curriculum Development.—
The President of the Defense Acquisition University shall work with the relevant professional schools and degree-granting institutions of the Department of Defense and military departments to ensure that best practices are used in curriculum development to support acquisition workforce positions.
Cooperative Research and Development Agreements.—
In engaging in research and development projects pursuant to subsection (a) of section 2358 of this title by a contract, cooperative agreement, or grant pursuant to subsection (b)(1) of such section, the Secretary may enter into such contract or cooperative agreement or award such grant through the Defense Acquisition University.
The Defense Acquisition University shall be considered a Government-operated Federal laboratory for purposes of section 12 of the Stevenson-Wydler Technology Innovation Act of 1980 (15 U.S.C. 3710a).
Source
(Added Pub. L. 101–510, div. A, title XII, § 1202(a),Notes
Amendments
Effective Date
Training in Commercial Items Procurement
Training.—
Not later than one year after the date of the enactment of this Act [
The origin of part 12 and the congressional mandate to prefer commercial procurements.
The definition of a commercial item, with a particular focus on the ‘of a type’ concept.
Price analysis and negotiations.
Market research and analysis.
Independent cost estimates.
Parametric estimating methods.
Value analysis.
Best practices in pricing from commercial sector organizations, foreign government organizations, and other Federal, State, and local public sectors organizations.
Other topics on commercial procurements necessary to ensure a well-educated acquisition workforce.
Enrollments Goals.—
The President of the Defense Acquisition University shall set goals for student enrollment for the comprehensive training program established under subsection (a).
Supporting Activities.—
The Secretary of Defense shall, in support of the achievement of the goals of this section—
engage academic experts on research topics of interest to improve commercial item identification and pricing methodologies; and
facilitate exchange and interface opportunities between government personnel to increase awareness of best practices and challenges in commercial item identification and pricing.
Funding.—
The Secretary of Defense shall use amounts available in the Department of Defense Acquisition Workforce Development Fund established under section 1705 of title 10, United States Code, to fund the comprehensive training program established under subsection (a).”
Training on Agile or Iterative Development Methods
In General.—
Not later than 180 days after the date of the enactment of this Act [
Course Elements.—
In general.—
The course shall be taught in residence at the Defense Acquisition University and shall include the following elements:
Training designed to instill a common understanding of all functional roles and dependencies involved in developing and producing a capability using agile or iterative development methods.
An exercise involving teams composed of personnel from pertinent functions and functional organizations engaged in developing an integrated agile or iterative development method for a specific program.
Instructors and content from non-governmental entities, as appropriate, to highlight commercial best practices in using an agile or iterative development method.
Course updates.—
The Secretary shall ensure that the course is updated as needed, including through incorporating lessons learned from the implementation of the pilot programs required by sections 873 and 874 of this Act in subsequent versions of the course.
Course Attendance.—
The course shall be—
available for certified acquisition personnel working on programs or projects using agile or iterative development methods; and
mandatory for personnel participating in the pilot programs required by sections 873 and 874 of this Act from the relevant organizations in each of the military departments and Defense Agencies, including organizations responsible for engineering, budgeting, contracting, test and evaluation, requirements validation, and certification and accreditation.
Agile Acquisition Support.—
The Secretary and the senior acquisition executives in each of the military departments and Defense Agencies, in coordination with the Director of the Defense Digital Service, shall assign to offices supporting systems selected for participation in the pilot programs required by sections 873 and 874 of this Act a subject matter expert with knowledge of commercial agile acquisition methods and Department of Defense acquisition processes to provide assistance and to advise appropriate acquisition authorities of the expert’s observations.
Agile Research Program.—
The President of the Defense Acquisition University shall establish a research program to conduct research on and development of agile acquisition practices and tools best tailored to meet the mission needs of the Department of Defense.
Agile or Iterative Development Defined.—
The term ‘agile or iterative development’, with respect to software—
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
involves—
the incremental development and fielding of capabilities, commonly called ‘spirals’, ‘spins’, or ‘sprints’, which can be measured in a few weeks or months; and
continuous participation and collaboration by users, testers, and requirements authorities.”