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

Consulting with Agile or DevOps

Viktor Farcic: When you consult for companies with Agile or DevOps, do you have a prescriptive type of approach? For instance, thou shalt do Scrum!

Liz Keogh: Thou shalt learn Cynefin because it's pretty much the first thing I teach. After that, if you want to start with Scrum, go ahead. I think Scrum is a great way to get started, especially if it's a new project and you don't have anything in play already.

Typically, large organizations have already done a bunch of analysis work. We talk about how great it would be if we had this flexible scope, but most organizations have already done three months' worth of UX research and analysis, and it tends to constrain things. So, let's slice it up vertically; let's work out what the most important bits are and deliver those first—where are the risky bits, where are the highest-uncertainty bits, and where's the new stuff?

Let's do those first and do it early. Let's...