The recent TSB migration debacle was more than an Ops project and had Dev, testing and customer impacts. In these days of Ops/Dev collaboration, should it have been run as a DevOps-style process – or was it run “DevOps in name only”?
The dimensions that optimise Knowledge Work differ to those that optimise Manual Work:
Complex Work over Complicated Work.
Value, Flow, Quality over Cost, Time and Scope.
Culture over Processes.
Using the same terminology as the Agile Manifesto, although we value the statements on the right, we value the statements on the left more…
All great artists have their tools – Thor has a hammer; Captain America, a shield; Lara Croft, a bow; David Hasselhoff, Kit; Iron Man, a multi-functional suit; Michelangelo, a chisel; Yehudi Menuhin, a violin; Picasso, a paint brush; Ronaldo, a football; etc. These tools generally amplify the character of the user. They become an extension of the individual and as a result, the wielder can do significantly more than without them, a good quality tool is worth it’s weight in gold.
This is the next in the series of articles on DevOps. Today, the topic is about teams and productivity. Now, like most of you, I am conditioned to find out what needs doing before finding the people who need to do it. This sounds sensible and logical and for most ‘Good’ organisations, this is fine. However, Collins, found that Great Companies start with ‘Who’ first – the difference between Level 4 and Level 5 Leadership.