Attempts by the U.S. Department of Defense (DoD) to address persistent challenges with software development have been hampered by an inability to identify the many software professionals working within DoD's programs. In this report, the authors identify and characterize a subset of DoD's software workforce, the types of software developed within DoD, and the variety of methods DoD programs use when employing that workforce to develop software.
The Composition and Employment of Software Personnel in the U.S. Department of Defense
An Initial Analysis
Published Dec 24, 2020
- What is the composition of the DoD workforce tasked with developing software? Specifically, in what DoD career fields do they work, how experienced are they, what is their educational background, and what software development activities do they perform?
- What type of software is DoD developing, and what are the implications for developing and training DoD's software workforce?
- How is DoD using current and emerging practices and methods for both software development and workforce development and employment?
The U.S. Department of Defense (DoD) has experienced persistent challenges with software development across various acquisition programs. Attempts to address those challenges through workforce initiatives (such as hiring, training, and professional development) have been severely hampered by an inability to identify and characterize the presumably tens of thousands of software professionals working within DoD's programs.
In this report, the authors attempt to identify and characterize DoD's software workforce, the types of software developed within DoD, and the variety of methods DoD programs use when employing that workforce to develop software. The research team's effort to develop a comprehensive picture of the software workforce was hindered by a lack of data in existing DoD databases and by internal DoD organizational issues that limited the team's ability to gather data. Although this report provides a snapshot of DoD's software workforce, the types of software developed within DoD, and the variety of methods DoD programs use when employing that workforce to develop software, there are significant limitations in the underlying data. The research team's recommendations, using lessons learned from this effort, focus on what defense leaders will need to better understand, train, and employ DoD's software acquisition workforce in the future.
Findings regarding the composition of DoD's software workforce from a snapshot of about 2,000 personnel
- Uniformed personnel, for the most part, do not identify as being part of the software workforce.
- The vast majority (about 80 percent) of DoD software personnel in the sample are in the engineering acquisition career field.
- About half of DoD's software personnel in the sample have a degree related to software or computer science; more than 90 percent have a degree in science, technology, engineering, or math.
- Most personnel with an educational background in software or computer science spend at least a portion of their time developing software. Less than 3 percent are employed exclusively in management roles.
Distinct challenges of DoD software
- Most DoD software directly supports the war fight—i.e., software contained in radios, sensors, and weapons, as well as in air, space, and land vehicles.
- Most DoD software is tightly integrated with underlying hardware.
- DoD software's security and safety challenges are far greater than for most commercial software development efforts.
Distinct challenges of DoD software organizations
- Many contributing factors make it difficult to hire software developers into DoD acquisition organizations.
- Once hired, there are substantial barriers to keeping software skill sets current.
- Software project, program, and contract management are key skill sets needed by DoD's software workforce as the department strives to manage a much larger contractor workforce.
- It is imperative that DoD develop the competencies and culture needed to incorporate actual warfighters early and often in the development of programs and the underlying software.
- When seeking to reap the benefits of commercial software development practices, DoD must take care not to replicate the security practices of that industry.
- DoD should review current safety standards and guidance to ensure they include best practices for achieving high levels of operational trust in highly automated and/or autonomous DoD software–intensive systems.
- DoD software workforce development initiatives should be focused on the best practices of embedded software development.
- Improvement initiatives should focus on engineering acquisition careers, given that most personnel in the DoD software workforce are assigned to that field.
- Additional efforts are needed to identify and characterize DoD's software workforce. Those efforts must be driven from the highest levels of the DoD hierarchy.
- Future software workforce research teams should include one or more government personnel from the software centers as detached members of the project team.
- Once the software workforce has been identified, DoD should conduct analyses to better understand how the dynamics of age, experience, and pay levels affect hiring and retention.
- DoD should conduct an in-depth analysis regarding the employment of software-educated professionals to ensure that biases regarding suitability for assignment into broader roles are not affecting promotions.