You can't improve a cog

I was advising somebody who had been tasked with improving a single process. I said that without a systemic improvement of all the processes and the technologies and the people around it, trying to improve one process is like trying to improve one cog in the machine.

ITIL exam market continues to shrink

It's not as if too many people really care anymore, but the ITIL market appears to continue to shrink.
I haven't kept an eye on the numbers for a while - having more important things to think about these days with DevOps - but a comment on this blog triggered me to go look again. Yup, still falling.

The IT engineering fallacy

There are some fundamental fallacies which have misled IT in the past and one of them is "the engineering fallacy", the false belief that we build IT systems like engineers build bridges.

Merry Christmas from the IT Skeptic

Merry Christmas and a happy New Year to all my readers and followers.
Image

I really appreciate you folks. Without your support there wouldn't be any point in this blog going on for over a decade.

Axelos are the Official source of DevOps now?

Imagine my surprise to discover at the recent DevOps Enterprise Summit conference that Axelos are now the official source of DevOps.
Image

The two tribes of DevOps

DevOps works to unite Dev and Ops communities to remove the vertical fracture in our IT organisations.
Ironically in the process of doing this we appear to be fracturing on a horizontal line between those oriented towards technology, software and coding, and those oriented towards business, people and practice.

Get out of the way

A basic principle of DevOps is for "Necessary Non-Value Work" to get out of the way of Value Work.
© Copyright canstockphoto.com

In the Require-to-Deploy value stream, this NNVW includes

  • security
  • architecture

Railroads don't have a batch size of 1

Lean theory tells us that the optimal batch size is 1 [update: no it doesn't. Optimal batch size is often 1, especially in a manufacturing context.]
i.e. we perform each unit of work on demand and it flows independently through the value stream.
Certainly that is the case when you order one of my books which are printed on demand individually and posted directly to you.
Image
I am still learning about systems and flow. Some of you will know that I am a train nut: I like railways. So it puzzled me to read an article recently in Trains magazine about the trend to larger trains, which have increased by a factor of 100 over the last 150 years.

How hard can it be?

An analogy for our IT reality:

What's so hard about building a road?
Here's a fun Twitter conversation:

Eating the elephant

Some analogies are even more useful if you unpack them a bit more. For example, here is my take on eating the elephant:

Sure you can eat an elephant one bite at a time but sooner or later you are still left with a huge carcass you need to heave into a skip [dumpster].

Syndicate content