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)

The difference between DevOps and Agile

Viktor Farcic: Let's talk more about the evolution from Agile to DevOps. What exactly did you mean by that?

Julian Simpson: I came to the Agile movement reasonably late in its development. I wasn't around to see some of the earlier Agile projects, but my understanding is that we solved some of the problems of how we know what to build and how we should go about planning and delivering the build in an iterative fashion. Once you've solved that problem, there are engineering challenges, such as integration. There's no excuse for having a huge merge phase at the end of your project now because continuous integration has been a thing since at least the late 1990s.

"DevOps is the response to solving problems that you have when you're successful in the earlier stages of your project's evolution."

—Julian Simpson

You'll find other problems that you didn't have originally because you...