A Story of DevOps >> Episode 10. The Suit (Digital Transformation)
Digital Transformation are two words being used by so many people – But do we really understand what this is?
Using the “Iron Man” analogy, I have had a go at explaining…
Tagged: DevOps
DevOps, an IBM Perspective – it’s going to be a culture thing for the Mutable Business, not just a technology thing, and most of IBM’s ideas have general application
I’ve just had an interesting conversation with a couple of DevOps people from IBM, Eric Minick, OM lead for DevOps and James Hunter strategy lead for DevOps. IBM defines DevOps as an “essential enterprise capability for the continuous delivery of software-driven innovation that enables organizations to seize market opportunities and reduce time to customer feedback” (see here). We agreed that DevOps was very much a “culture thing” rather than a “technology thing”, although Eric did point out that the Kubernetes container orchestration software is an important enabler, from the IBM point of view. It is what helps one to produce
A Story of DevOps >>Episode 9. Kryptonite (DevOps Anti-Patterns)
Do you know that as Superman’s powers are destroyed by Kryptonite, DevOps powers are destroyed by Anti-Patterns – read on.
A Story of DevOps >> Episode 8. Balrog (Confront the Brutal Facts)
“The moment a leader allows himself to become the primary reality people worry about, rather than reality being the primary reality, you have a recipe for mediocrity, or worse. This is one of the key reasons why less charismatic leaders often produce better long-term results than their more charismatic counterparts” Good to Great, Collins
A Story of DevOps >> Episode 7. Jedi (Practices and Mastery)
In previous articles, we have talked about the Force which consists of great leaders, vision, product teams, tools and environment, let’s now discuss the principles behind the practices.
Future starting here? Looking at DevOps processes beyond simple software development
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”?
