It was awesome to have a DevOpsDays conference right here in my home town of Melbourne. I was super excited to be going. The 2 day conference was sold out. This alone shows the amount of interest in DevOps at the moment.
The views below are my own and do not represent the opinions of my employer.
Day 1 kicked off with a welcome from organizer Lindsay Holmwood.
The keynote was by none other than the “Father” of DevOps Patrick Debois.
His slides are here What’s in a word
A few people are getting too hung up on what the word means. Is it too exclusive? What about the Business, Test/QA, Network, Storage etc etc… people. Is it a job title now?
I really like the term “Frictionless IT” that sums up what DevOps is.
Does DevOps need a manifesto? Patrick doesn’t think so. Try reading the Agile manifesto with an open mind and think holistically, rather than focusing on software. i.e. Working infrastructure is the primary measure of progress.
Can DevOps work within an ITIL organization? Yes it can. If you don’t let bureaucracy get in the way too much.
Second up was “Kanban for IT Operations” from Jason Yip from Thoughtworks.
His slides are here Lean and Kanban for IT Operations
A great overview of Kanban and why it works for Ops as well as Dev. I heartily second this.
There was an interesting question from the audience “what is a good rule of thumb for Work In Progress (WIP) limits”, the logical answer is “measure the effect of changing the WIP limit and see what happens”.
3 tasks per person was suggested. I’d start with 2. The objective is to keep the number of tasks “in progress” small, and throughput high. Don’t be afraid to move tasks out of the “in progress” state.
Jason’s message for me was don’t be afraid to experiment with processes. Measure the effect of changes and optimize.
Next was Nish Mahanty from MYOB talking about “Building High Performing Teams”.
Takeaways for me were the importance of aligning whatever motivates dev and ops. Also sounds like MYOB know the importance of connecting with their customers. Nish said ops/dev guys listened in on support calls from users of their products to get a better feel for their pain points. Awesome stuff.
Next was a panel discussion. Link to video coming?
Unfortunately there are no silver bullets. Or silver guns.
After lunch were the Open Spaces sessions.
I’m sorry, but I don’t find these are as satisfying a format. I really like 5 minute Ignite talks more.
It was interesting to hear Google’s take on DevOps via Paul Cowan. The Site Reliability Engineer (SRE) at Google is really the glue that keeps everything running. Google also have Software Engineers and guys who deal with the hardware… more traditional System Administrators, Network Administrators etc…
But the SRE guys are “practically perfect” 🙂 They know about how Google works from a holistic perspective that the developers mightn’t have. They mentor developers. They cut code. They go on-call. (This sounds terrifying.)
Google puts developers on-call for the first weeks of launching a new product. Brilliant.