Book Image

DevOps Paradox

By : Viktor Farcic
Book Image

DevOps Paradox

By: Viktor Farcic

Overview of this book

DevOps promises to break down silos, uniting organizations to deliver high quality output in a cross-functional way. In reality it often results in confusion and new silos: pockets of DevOps practitioners fight the status quo, senior decision-makers demand DevOps paint jobs without committing to true change. Even a clear definition of what DevOps is remains elusive. In DevOps Paradox, top DevOps consultants, industry leaders, and founders reveal their own approaches to all aspects of DevOps implementation and operation. Surround yourself with expert DevOps advisors. Viktor Farcic draws on experts from across the industry to discuss how to introduce DevOps to chaotic organizations, align incentives between teams, and make use of the latest tools and techniques. With each expert offering their own opinions on what DevOps is and how to make it work, you will be able to form your own informed view of the importance and value of DevOps as we enter a new decade. If you want to see how real DevOps experts address the challenges and resolve the paradoxes, this book is for you.
Table of Contents (21 chapters)
20
Index
21
Packt

The relationship between DevOps and Agile

Liz Keogh: DevOps used to be when you did Agile with a small team; back then, it was just developers in small, cross-functional teams who were writing code directly for the customers. The customers would give the DevOps team their requirements; the developers would then develop the code and give it back to the customers. Now you've got much larger enterprise organizations where operations is a separate department, and possibly even a separate company within the larger group, and yet you still want to ship stuff. I always say that DevOps is a good start.

"DevOps used to be when you did Agile with a small team; back then, it was just developers in small, cross-functional teams who were writing code directly for the customers."

—Liz Keogh

Agile generally starts with the development teams. You've likely got some business analyst types, testers, and developers all writing the code, and then they think...