Before there was “C2D2,” the Star Wars-evoking acronym for Lockheed Martin’s F-35 upgrade program, there was the F-22 Raptor’s “Scaled Agile Framework,” or SAFe.
The F-22 was the first Pentagon weapon system to implement “agile” software and hardware development methods. The Raptor modernization program transitioned from a more traditional approach to the SAFe method in 2014, in an attempt to reduce the number of deficiencies encountered during flight testing and to deliver capabilities to the warfighter faster.
Now, as the F-35 shifts to an “agile” development approach for its own modernization road map, the Joint Program Office (JPO) may do well to take some lessons learned from SAFe.
Instead of developing software in one large package, or block, SAFe uses 12-to-14 week periods to develop smaller portions of software that contribute to the final product. Under SAFe, software developers perform integrated testing during the development process, which they hope will reduce the number of deficiencies identified during flight testing and the number of unplanned software updates. 
The upgrade program, which was established in 2003 and will run until 2026, will add critical capabilities to keep the F-22 relevant over its lifetime: Link 16, the tactical communications data link used by most fighter aircraft; enhanced friend-or-foe identification capabilities; sensor enhancements; a Helmet Mounted Display and Cuing System for improved tracking, targeting and weapons controls; and better defenses against jamming.
But the Pentagon’s Inspector General was critical of the U.S. Air Force’s management of the F-22 modernization program in a March report, particularly the contracting approach