Loading summary
A
You're listening to the Cyberwire Network powered.
B
By N2K.
A
And now a word from our sponsor ThreatLocker. The powerful Zero Trust Enterprise solution that stops ransomware in its tracks. Allow Listing is a deny by default software that makes application control simple and fast. Ring Fencing is an application containment strategy ensuring apps can only access the files, registry keys, network resources and other applications they truly need to function. Shut out cybercriminals with world class endpoint protection from Threat Locker.
B
The word is Agile Software development method spelled agile as in the ability to move quickly and freely software as in computer programs designed to perform well defined functions development as in the people, process and technology used in creating, designing, deploying and supporting software and method as in a particular procedure for accomplishing a task. A software development philosophy that emphasizes incremental delivery, team collaboration, continual planning, and continual learning. Example Sentence Agile is a mindset that drives an approach to software development. Origin and context in 1956, Herbert Bennington invented the first version of the waterfall software development method. Interestingly, Bennington didn't get credit for his work early on. Another guy, Dr. Winston Royce, in 1970 got the credit when he published a criticism of the model that didn't even mention it by name, but the paper had nice diagrams that showed the process, requirements, analysis, design, implementation, testing, and operations all flowing from top to bottom just like a waterfall. In 1976, Bell and Taylor referred to the Royce diagrams as the Waterfall model, and the name stuck to Dr. Royce. In 1985, the US Department of Defense adopted the waterfall model as a requirement for all contractors despite Royce's criticism, and started a period of ponderous, iceberg like progress in producing software. The impact was that many programming projects took years to finish, and the team spent as much time documenting their requirements as they did writing code. In the 1990s, some rebel developers started experimenting with ways to improve the process. They began toying with the Rational unified process in 1994, the scrum in 1995, and extreme programming in 1996. But in February 2001, 17 men and yes, they were all men. We can have a longer discussion later, but about the misogyny of the IT community. In the early 2000s, they all traveled to Utah for a long weekend of skiing and discussions about building software. The result was the Agile Manifesto, a rejection of the waterfall model and an embracement of the idea of producing real working code as a milestone of progress. The manifesto laid out four key individuals and interactions over process and tools, working software over comprehensive documentation, customer collaboration over contract, negotiation, and responding to change over following a plan. The Agile method helped push big software development ideas like infrastructure as code, DevOps and DevSecOps. And the impact was that the waterfall method produced new code once every three years or so. The Agile method made it possible for 10 new deployments a day. Nerd Reference In 2009, Stanford University's E Corner interviewed Barbara Liskoff, one of computing science's founding mothers who received the association of Computing Machinery's Turing Award in 2008 for her contributions to solving the software crisis of the 1980s. She had this to say about her work and the work done by others to solve the problem.
C
I was at NIDRR and they do research for the government and I was asked to look into this problem that the government was interested in, namely what to do about the software crisis. So the software crisis was people would build big programs and they wouldn't work. They spend millions of dollars, hundreds of man years, and in the end they'd have to scrap the whole thing. And actually, in the 60s, the 70s, the 80s, you could read in the newspaper about these fiascos. Companies such and such spend all this money and now they've had to throw the whole thing away. So the software crisis was a really big problem. And I was asked to start thinking about this. And so I started to look into this field. It's called programming methodology. Of course, I read all the papers that existed and there were some really good people working in that field. There was Edsger Dijkstra, Tony Hoare, Dave Parnas. I mean, these were very good people. And they were writing papers about how do you break up a program into pieces so that you can reason about it. The problem that they were worried about was software programs are huge. They were huge then, millions of lines of code. They're even bigger today. There's no way that you can make sense of something that big. You have to have a way of breaking it up into small pieces that you can work on independently, reason about independently, and that somehow you put the whole thing together and it works. And nobody knew how to do that.
B
Wordnotes was written by Sammy Diggs and Tim Nodar, executive produced by Peter Kilping and edited by John Petrick and me, Rick Howard. The mix, sound, design and original music have all been crafted by the ridiculously talented Elliot Peltzman. Thanks for listening.
A
And now a word from our sponsor. The Johns Hopkins University Information Security Institute is seeking qualified applicants for its innovative Master of Science in Security Informatics degree program. Study alongside world class interdisciplinary experts and gain unparalleled educational research and professional experience in information security and assurance. Interested U.S. citizens should consider the Department of Defense's Cyber Service Academy program, which covers tuition, textbooks, and a laptop, as well as providing a $34,000 additional annual stipend. Apply for the fall 2026 semester and for this scholarship by February 28th. Learn more at CS JHU. EDU MSS.
Host: N2K Networks
Date: August 19, 2025
Theme: Origins and significance of Agile methodology in software development, with reflections on the "software crisis" and the pivotal shift from Waterfall to Agile approaches.
This episode explores the historical development, core principles, and ongoing impact of the Agile Software Development Method. Through a detailed narrative, the host explains why Agile emerged, how it's defined, and how it transformed software production. The episode features a notable quote from Turing Award-winner Barbara Liskov on tackling the software crisis, highlighting the evolution from monolithic software projects to today's collaborative, incremental approaches.
“A software development philosophy that emphasizes incremental delivery, team collaboration, continual planning, and continual learning.” (00:51)
“Agile is a mindset that drives an approach to software development.” (00:51)
“A period of ponderous, iceberg-like progress in producing software.” (01:54)
"The Agile method made it possible for 10 new deployments a day," compared to "the waterfall method [which] produced new code once every three years or so." (03:35)
On the Waterfall’s inefficiency:
“The impact was that many programming projects took years to finish, and the team spent as much time documenting their requirements as they did writing code.” (01:54)
On Agile’s revolutionary shift:
“The Agile method made it possible for 10 new deployments a day.” (03:35)
Barbara Liskov on the software crisis:
“Companies...spend all this money and now they’ve had to throw the whole thing away. So the software crisis was a really big problem.” (04:54)
The episode uses a conversational yet informative tone, blending technical history with relatable storytelling and moments of wry humor (noting, for example, the all-male Agile Manifesto summit and broader industry context).
This episode provides a compact yet rich exploration of the Agile Software Development Method, placing its origins in the context of a slow-moving, crisis-ridden industry, and tracking its explosive effects on software processes. By spotlighting firsthand experiences from computing pioneers and making jargon accessible, the show offers both a history lesson and practical understanding of why Agile matters today—perfect for anyone interested in the past and future of software development.