devops

Great DevOps books to read

As if anyone reads books any more. I'm drowning in great books to read while the Internet gives me endless distractions. My attention span is shot to hell, and my memory has been replaced by Google.

But sometimes I find a few minutes and here are some of my favourites for understanding this beast called DevOps. [Updated 14/11/2019]

Reflections on the DevOps Enterprise Summit UK 2016

I just got back to the last rock on the planet, all the way from London and the DevOps Enterprise Summit UK. It was worth all the travel. IT Revolution run a great event.

Who owns DevOps?

There is currently a tension in the DevOps world, between influential purists saying you cannot define, codify, or certify DevOps, and most of the world saying it is bloody well going to anyway if DevOps is to be useful in the mainstream.

Don't reorg for DevOps

The point of DevOps is to span silos not create new ones.

I'm seeing too much of enterprises assuming one of the first steps of DevOps is a reorganisation.

If DevOps is about collaboration across silos, how does rearranging the silos help? DevOps isn't about org structures.

Challenging the operational rites

Over time a strange set of rites and rituals grow up around the Require-to-Deploy value stream*. Some of them are there to protect the quality of the output but others have ceased to add value.
Image

Conflicting principles

A client was developing a set of principles to guide a DevOps transformation and I proposed the two following principles to be included:

  • Honour existing processes, records, and controls. They arose for a reason.
  • Streamline and simplify all processes, records, and controls. Challenge the level of ceremony.

Noble Failure

It's OK to fail.

DevOps Training Options

The DevOps training space has become complex which is no surprise given that it is an open community with no central governance, so I thought it was time to canvass the DevOps training options for you in a single place.

DevOps and ITIL are both ITSM

DevOps and ITIL are both ITSM. The patterns are the same though the execution is different.

DevOps is only looking at one of four IT4IT value streams

The new IT4IT™ standard maps four value streams in IT. DevOps is concerned with one of them. What happens when we apply the the same ideas to the other three?
[If I wrote that headline again, I would insert the word "mostly"]

Syndicate content