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.
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.
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"]
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.
When there is talk about an "operating model" do you nod wisely and wonder WTF they are actually talking about? I did for years. In my consulting work I got my head around what it actually is. Here are some ideas.