devops

OGC re-forms to create DevOps body of knowledge

The Efficiency and Reform Group of the UK Cabinet Office are about to announce that the Office of Government Commerce (OGC) will be resurrected immediately in order to develop a British standard DevOps.

How DevOps messes with your head

For an old man like me, some of the concepts sweeping our industry as part of the current IT Renaissance are quite challenging. They challenge our fundamental axioms or assumptions which underpin our whole approach to IT.

An important DevOps word: toolmakers

The word "toolmaker" has great explanatory power to help IT people understand how their world is changing. Those who come from the Run domain of IT (as compared to Build) are becoming toolsmiths.

What is a DevOps role

There is some confusion when organisations organise or advertise for "devops" skills or roles.
I think there are at least three "devops" skills / roles you could potentially be asking for:

The IT Liberation Movement - an IT Renaissance

[Update: At the DOES15 conference, I think George Spafford finally nailed the name of this for me: an IT Renaissance ]

Considerations for Multi-Speed IT

Recently I posted about the "Big idea" I am focused on for 2015: Multi-Speed IT Capability. Let's drill down into some of the further considerations that come out of that.

Multi-Speed IT

© Copyright Canstock Photo IncEnterprises are wrestling with the conflicting needs to chase competitiveness in a world of endlessly changing technology, whilst still remaining mindful and careful. In IT we are caught in the same bind. I have written about this squeeze before in "To Protect and Serve".

This year I'm looking at solutions: how IT can deal with the dichotomy with Multi-Speed IT. By embracing Agile, DevOps, BYOD and other "liberation" approaches, and integrating them into our ITSM, risk, and governance practices, we can create an IT environment with a better chance of responding at the speed of business, whatever the business chooses that speed to be. This article proposes a nuanced approach to two-speed IT, where each lifecycle implementation is a blend of the two "speeds".

Who owns the system during the go-live warranty period?

Transitioning a project into Production is a complex process. One of the trickiest parts is transitioning responsibilities.

"Go-live" is sometimes seen too simplistically as a handover to Operations, as if Ops will magically run it from Day One without help. Or DevOps sees it the opposite way, where Operations plays a minor role forever.

There needs to be a transitional phase.

DevOps Unicorns Horses and Mules

DevOps folk use the terms "unicorns" and "horses" as if everybody understands what they mean. Quite possibly you don't. So here's the gist:

DevOpsRun: DevOps is great but what about Run?

Is there a bigger picture than DevOps? (I defined it here). In theory no, it encompasses the whole IT lifecycle of services. But in practice it seems to me much DevOps discourse is still Build- and Transition-centric. We can expand thinking to all of DevOpsRun.

Syndicate content