3 years ago

Category: Software, Infrastructure, automation

We are going to pause technology development for a moment and talk about a shift in procedures and mentality that started at the beginning of the 2000’s. As we already discussed in the first part of this series, in an on-premises environment without automation tools or virtualization employed, this led to a conflict between the development team, which was pushed to integrate new code quickly into the code base and the operations team, which (justifiably!) feared system instability due to changes.

To improve this situation, a handful of people interested in software development got together in 2001 to write the Agile Manifesto, addressing the challenges software development faced at the time and proposing a better way. It was proposed that software should be developed in iterative cycles making the development process more flexible and more adaptive to changes of requirements.

Devops is about how all of this is put together in a way that it improves the quality of a software product, but also the efficiency and well-being of the teams working on it.