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 and ITIL are both ITSM

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

The IT Skeptic's tenth birthday post: on Optimism

May 16th was a special day for me: ten years since the first post on this blog.
I've had my ups and downs but I'm still going strong (though some would say I've grown too mellow).
How to mark the day? Instead of some self-indulgent retrospective, I'd like to recognise the occasion by publishing a second edition of "the Worst of the IT Skeptic" book. I'd like to but I wont, because after all these years I still haven't got around to a revision of any of my books. So instead let's talk about optimism.

Service catalogue and request catalogue

It is hard to believe that confusion between service catalogue and request catalogue is still a thing but it is, as shown by a recent conversation on Facebook Back2ITSM.

Cloud solves everything in bi-modal ... not. Cloud is one small piece of DevOps

This article "Meeting the challenges of bimodal IT" contradicts itself:

separation of old legacy systems, people and processes from new, mostly cloud-native systems, people and processes.

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