Publication

The University of Southern California (USC) and its Information Sciences Institute (USC/ISI) undertook research into improving the space-based systems acquisition process through the adoption of agile and DevSecOps methodologies. The USC/ISI team undertook research and systems engineering analysis to explore the mission engineering methods, analysis, metrics and training needed to transition from a traditional DoDI 5000.02 waterfall development environment to an agile/DevSecOps space systems acquisition environment. Over the two-year period of the project, the project team has been embedded at the U.S. Space Force’s Space Systems Command, Military Communications and Positioning, Navigation, and Timing directorate (SSC/CG developing performance measuring tools, collecting performance metrics and providing subject matter expertise on an on-going long-term highly agile development effort that is subject to traditional waterfall acquisition reporting requirements. Based on observations and analysis of data collected over the past two-years, the USC/ISI team developed the following recommendations regarding transitioning from a traditional DoDI 5000.02 waterfall environment to an agile/DevSecOps development environment. While these recommendations are focused on software-only developments, many of them are also relevant to hardware or hybrid hardware/software environments.

• There is still a need for upfront systems engineering in agile/DevSecOps environments. At a minimum, such engineering is required to help populate the project backlog.
• The acquisition of a near-operational environment should be the highest priority task on the project backlog. A fully functioning DevSecOps pipeline can’t be implemented without such an environment.
• During feature and story planning, the focus should always be on MVPs and MMPs and not on meeting feature/story velocity goals.
• Get all intellectual property (IP), licensing and third-party contracting completed upfront prior to the start of development.
• Add margin to the schedule and budget to allow for the customization of performance tracking tools. Many tools cannot be used due to foreign-ownership, licensing and configuration challenges.
• Government participation in scrums, demonstrations, and other ceremonies is essential for increased situational awareness of the project. This participation needs to be well managed to ensure personnel don’t become fatigued or over-tasked.