Unfortunately it is still practiced in many environments, including most Navy software acquisition efforts, which are frequently run under a "systems engineerin

Unfortunately it is still practiced in many environments, including most Navy software acquisition efforts, which are frequently run under a "systems engineering" process intended for hardware like ships and airplanes. This process includes multiple reviews in a "SETR" (System Engineering Technical Review) process (https://www.acqnotes.com/Attachments/SETR%20Navy%E2%80%99s%20Acquisition%20and%20Development%20Process%20and%20Software%20Lessons%20Learned.pdf https://www.acqnotes.com/Attachments/SETR%20Navy%E2%80%99s%2...), including steps like: * SRR (System Requirements Review) * CDR (Critical Design Review) * TRR (Test Readiness Review) Example of slide 15: Example of Items from SRR Template * SW Development Team * Integrated Mater Schedule Highlighted with Software Milestones * Software Entrance Criteria * Requirements Analysis and Allocation Methodology (sounds agile to me!) * System Specifications Tree * Contract Data Requirements List (CDRL) * Software Development Strategy * Software Development Process * SW Safety, Information Assurance and Security requirements * Software Supplier Management * Software Measurement * Software Risk Assessment with Mitigation Strategies * Issues and Concerns