It's the Ranger4 #DevOpsFriday5 series - today's contributor is Ingo Weber. He's DevOpstastic!
1) What’s your preferred definition of DevOps?
For our new book “DevOps: A Software Architect's Perspective” we looked at many definitions, and finally came up with this one:
"DevOps is a set of practices intended to reduce the time between committing a change to a system and the change being placed into normal production, while ensuring high quality."
Our definition of DevOps focuses on the goals, rather than the means, so we don’t talk about communication, collaboration, agile methods, etc. If a practice is intended to reduce the time between a commit from a developer and deploying into production, it is a DevOps practice according to our definition. It should be noted, though, that the goals specified in the definition do not restrict the scope of DevOps practices to testing and deployment – in order to achieve them, you might want to adopt certain monitoring practices, or consider Ops needs during requirements collection. Also, the ‘high quality’ aspect concerns both the system and the delivery mechanism of choice, and implies reliability and repeatability.
The first pass of the book is completed, and the chapters are currently available for public review here – but note that the above definition is not included in the first version. The book will be published early to mid next year.
2) When people ‘do’ DevOps, what’s the most common mistake you see them make?
From our research, renaming an existing team to DevOps seemed to be a relatively common mistake.
Acting on a too shallow understanding of DevOps would rank quite highly as well.
3) How do you recommend an organisation new to DevOps start?
Read our book ;-)
More seriously: pick a new project that is run primarily by people who are eager (or at least willing) to try new stuff, get buy-in from the stakeholders to run it DevOps-style, and have a go!
4) What’s your prediction for what DevOps will look like in 2020?
Very abstractly speaking, the principle of getting “producers” involved in the operation, and hence thinking about operations when designing or producing something, will become much more prevalent. This will range from business folks specifying and maintaining website rules (such as showing special offers to certain customer groups, which you can start to see already), to goods which are currently sold as is, like cars or toasters, to … many things we can’t even imagine yet.
And some organizations will face the issue that they have to make deliberate decisions on how quickly they want to innovate – they’ll be so good at churning out new versions that they run the risk of overpowering their users with all the new features and changes in the UI.
5) Where do you like to go to get a DevOps hit?
I like the DevOps lists on LinkedIn since the contributions are quite diverse, and Devops Weekly for a more moderated format.About Ingo
Dr. Ingo Weber is a Senior Researcher in the Software Systems research group at NICTA in Sydney, Australia, as well as an Adjunct Senior Lecturer at the University of New South Wales (UNSW). He has published over 50 refereed papers, acted as a reviewer for many prestigious journals, including several IEEE and ACM Transactions, and has served as PC member for WWW, ICSOC, AAAI, and many other conferences. Prior to NICTA, Ingo worked for UNSW, and at SAP Research Karlsruhe, Germany.Follow Ingo:
Do you have something you'd like to say about DevOps? If you would like to be featured on #DevOpsFriday5 click the button below.