Chapter 24. Why InfoSec Practitioners Need to Know About Agile and DevOps
Fernando Ike
The release of the Agile Manifesto in 2001 was the consolidation of something that had already happened with many methods for application development such as extreme programming, Scrum, pragmatic programming, etc. They develop more efficient and robust features that the organization needs within a reasonable lead time. The Agile Manifesto was one of the foundation stones along with the internet revolution in the growth of digital-native organizations.
Over two decades after the Agile Manifesto, development and delivery features have become quicker than ever. This pressures operations IT teams to change their mindset and how they work, in order to know what developers and product managers were planning to deliver. Good communication and breaking silos have become essential skills.
In 2009, two events happened that changed how IT Operations must work:
John Allspaw and Paul Hammond presented “10+ Deploys per Day: Dev and Ops Cooperation at Flickr” at the Velocity Conference.1
Patrick Debois and others organized DevOpsDays in Ghent.2
Since then, we have seen new technologies, methods, and concepts concerning development, products, and operations. One key source organized by DORA Research and partners is the State of DevOps Report series.3
The 2019 DevOps State Report, organized by Google, shows ...
Get 97 Things Every Information Security Professional Should Know now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
