Here continues the DevOps Leadership Series interview with Jez Humble.
Chris: What are the top "takeaways" about DevOps people need to know? Not folks in the community but all of the other IT people who are NOW hearing the term.
Jez: DevOps is not a project you should start up,or a team you should create, or a person you should hire, or a product or solution or tool you should buy. DevOps is something you should be doing as part of process innovation or continuous improvement, which means everybody has to have enough slack time to work on it.
One common mistake organizations make (especially newcomers to lean) is thinking that time not spent on work products - building features or fixing bugs - is waste. That's like saying we shouldn't take time to maintain a jet engine because then we're not getting maximum utilization.
The engine of DevOps - and agile methodologies in general - is the retrospective. Teams need to reflect on what's going well and what's going less well and plan experiments to try and make things better. That could be doing some automation, trying out a tool, or buying lunch for the DBAs and discussing how you might work better together.
The most important bit of DevOps is the organizational change that it creates - money can't buy that.
Chris: is DevOps as a navigation device more than a fixed term, about more than the gap or pipeline between Dev and operations?
Jez: Yes. Dev and ops working together can improve things, but if we're just getting better at delivering and operating crappy services nobody wants to use, all you've done is got more proficient at shoveling shit.