Programmed to Fail - 3. Systems Analysis

Welcome to a special series on the acquisition talk podcast that gives you an audiobook tour of my research project titled, Programmed to Fail: The Rise of Central Planning in Defense Acquisition 1945 to 1975. I’m Eric Lofgren of the Baroni Center for Government Contracting at George Mason University. You can find this book for free and over 1,300 blog posts on my website, AcquisitionTalk.com. In this third episode, we look at the 1950s debates over how weapons development should proceed. The listener will find strong parallels to the modern debates over waterfall vs. agile development practices. Weapons development in the 1940s and 50s followed an agile method of iterative and incremental decisions made by small, empowered teams. Yet this practice became supplanted by the belief that iteration and competitive developments revealed a failure to plan, and that planning could relieve all uncertainties in weapons development. As you listen to the story, consider how weapons today are expected to proceed linearly from science, to prototyping, to full scale development, production, then operations and sustainment. There is little or no room for feedback mechanisms and learning. However, another important aspect of software today is not just agile development, but continuous development and deployment of capability in what is called devops. The lines between development and production are not as clear today as they were presented in the hardware-oriented world of the 1950s. Listen in on our third chapter of the Programmed to Fail story, this time focusing of the emerging religion of systems analysis, a religion which continues to pervade the defense acquisition system 70 years later. This podcast was produced by Eric Lofgren. You can follow me on Twitter @AcqTalk and find more information at AcquisitionTalk.com