; and (B) continuous participation and collaboration by users, testers, and requirements authorities. 885. Software development pilot using agile best practices (a) In general Not later than 30 days after the date of the enactment of this Act, the Secretary of Defense shall identify no fewer than four and up to eight software development activities within the Department of Defense or military departments to be developed using modern agile acquisition methods. (b) Streamlined processes Software development activities identified under subsection (a) shall be developed without incorporation of the following contract or transaction requirements: (1) Earned Value Management (EVM) or EVM-like reporting. (2) Development of Integrated Master Schedule. (3) Development of Integrated Master Plan. (4) Development of Technical Requirement Document. (5) Development of Systems Requirement Documents. (6) Use of Information Technology Infrastructure Library agreements. (7) Use of Software Development Life Cycle (methodology). (c) Roles and responsibilities (1) In general Selected activities shall include the following roles and responsibilities: (A) A program manager that is empowered to make all programmatic decisions within the overarching activity objectives, including resources, funding, personnel, and contract or transaction termination recommendations. (B) A product owner that reports directly to the program manager and is responsible for the overall design of the product, prioritization of roadmap elements and interpretation of their acceptance criteria, and prioritization of the list of all features desired in the product. (C) An engineering lead that reports directly to the program manager and is responsible for the implementation and operation of the software. (D) A design lead that reports directly to the program manager and is responsible for identifying, communicating, and visualizing user needs through a human centered design process. (2) Qualifications The Secretary shall establish qualifications for personnel