; (2) provide more effective tools and capabilities for developing, acquiring, and maintaining cyber tools and applications; and (3) create a repeatable, disciplined process for developing, acquiring, and maintaining cyber tools and applications whereby progress and success or failure can be continuously measured. (c) Consideration of agile software development, agile acquisition, and other best practices (1) In general The evaluation required by subsection (a) shall include consideration of agile software development, agile acquisition, and such 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), consider changes that would be necessary to established acquisition practices, including 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 conducting 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