ITSM and Cynefin – Lightning Blog

I attended the itSMF 20th Anniversary Conference in Melbourne this week and it was great to see the emphasis from many speakers about automation and using DevOps principles.

The Cynefin Framework is subjective and I was thinking about where many of us see the service management framework and ITIL on it. It is easy to imagine incident management in the chaotic domain and standard change management processes in the obvious domain (highly repeatable and therefore great candidates for automation).

So it was interesting to see the keynote from Lindsay Holmwood titled ‘Mixing Oil and Water: DevOps in an ITSM World’ where Lindsay busted the myth that DevOps and ITSM don’t mix. ITIL and the service management framework are great tools to identify the candidates for automation and for where to ‘build in’ governance to our continuous deployment pipelines.

If we want to get into the market with safe and small changes that take into account operability, security, regulatory requirements, and resilience, we really need to partner with our service management colleagues.

Assumption Pillows – Lightning Blog

Expanding the thoughts behind a recent tweet of mine.

‘Pondering….less obvious reasons…generate ‘pillows’ of assumptions…and are ineffective cushions against the sharp rocks of risk below’

Assumptions are like pillows – they are very comfortable and we are not aware of them for much of the time. The trouble is that our assumptions and the assumptions of other people that we are working with are likely to be different. When we don’t inspect our assumptions, we can overlook risks – so that is why our assumptions are like pillows.

It can feel like a waste of effort to inspect our assumptions – there are ways of working them into a workshop facilitation plan – that’s the easiest one to address.

Another way is to be aware of the feeling that something is not quite right in a conversation. Once I was negotiating a contract and almost starting to argue with the other party about a particular point – both of us thought that the other one was being a bit unreasonable. After a short break, we took a moment to clarify what we were discussing and it turned out that we both agreed the point, but had been discussing quite different things before the short break.

The main risk that assumptions cause in projects is delay. If we find ways to highlight assumptions earlier we can save wasted effort in circular discussions, rework or duplication.

It’s better to see the sharp rocks of risk than to cover them with assumption pillows.

LIGHTNING BLOGS – THE RULE OF THREES, OR THE RULE OF THIRDS.

LIGHTNING BLOGS
Welcome to the first in my lightning blog series. This series is for the ideas and observations we all make during our daily lives and rarely share or have time to explore them.

THE RULE OF THREES, OR THE RULE OF THIRDS.


The rule of threes is an observation I made while trying to save energy and money by examining and swapping light bulbs and the mode of generating the emitted light.
Sounds great and very intellectual but as usually happens you do something and then upon reflection realise there appeared to be a pattern. I actually was just trying to swap over to the newer 6 Watt LED bulbs, I had recently found in my local supermarket, to save money because my energy bills are creeping up there and starting to hurt (mother of invention).

I had swapped all the lights in my house with these 6 Watt LEDs, except for the two main lights in my kitchen and the dinning area. The reason these two lights hadn’t been swapped over, was that they were 18 Watt Fluorescent tubes. Well, finally the day came and I had decided it was time to do the swap. When I began to remove the fixtures, I noticed that they were not the original fixtures but had themselves been replacements for the type of light that was there previously. The original light fixtures were actually lamp holders, just like the type of fixture I was installing, great less touch up work.

Then it struct me, when the house was built the dominant form of lighting was incandescent bulbs. Incandescent bulbs ranged usually from 100 Watts to 60 Watts in your typical single light fixture for a room. Yes they made smaller bulbs 40 Watts and even as low as 20 Watts, but these were usually the bulbs used for bedside lamps or in chandeliers. The most likely scenario was that the original lamp holder would have held a 60 Watt bulb due to the small room size.

So what we had was a situation where if they had put a smaller bulb than 60 Watts the room would be poorly lite, however at the time, the more cost effective technology of fluorescent lighting would have meant a 20 Watt florescent tube would have given more light than the 60 Watt incandescent for a third of the cost. In fact the florescent tube would have probably given out the equivalent light from a 75 Watt bulb or more.

Now the fluorescent tube I was replacing was in fact, a newer more efficient 18 Watt florescent tube. Yet it struck me that I was now installing a 6 Watt bulb that was one third the wattage of the one I was removing. I also realised that the fluorescent must have been replacing a bulb at least three time the wattage as itself.

The rule of threes or thirds was born.
So did this mean that only when something became three times better or more efficient or used a third of the energy or effort, that we actually muster enough motivation or pressure to change?

Can the rule of threes be seen in other areas or even help us to decide when retooling or changing the way we work is most beneficial?

Like I said observations and ideas only in the Lightning Blogs. Food for thought and I hope the rule of threes or thirds may help in some way to guide you in your decision making.
Yes I know wattages do not equal Lumens but for simplicity, I didn’t go into that.
From Wikipedia : The luminous efficacy of a typical incandescent bulb is 16 lumens per watt, compared with 60 lm/W for a compact fluorescent bulb or 150 lm/W for some white LED lamps.

PS. Careful how you pronounce, The Rule of Thirds, it could be misunderstood as something else.