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.

There is no such thing as NoOps: it is an awful word

There is no term I detest more than "NoOps". NoOps means nothing runs, which means the business comes to a halt.

"NoOps" is provocative, alienating, patronising and demeaning to those who care about Ops. There will always be a science of making it run good and safe. There will always be Ops as an activity and function and skillset. Please erase this hideous word from your vocabulary.

Define DevOps: What is DevOps?

A reader asked me to define DevOps. It's not easy to find definitions. Here's mine.

Reflections on DevOps Enterprise conference

Recently I had the privilege to attend the DevOps Enterprise conference in San Francisco, hashtag #DOES14. Videos here.

That conference was put together by a number of people, but perhaps we owe it to this guy more than anyone: Gene Kim

where does DevOps work in the enterprise?

Gartner have been talking about bi-modal and tri-modal models of IT: some systems are legacy ones to be handled with legacy methods, with an emphasis on risk and control.

DevOps buzzword bingo

Buzzword Bingo is funny, but it is also a good test of whether you are across a topic. See how many of these words you know...

Syndicate content