It's the Ranger4 #DevOpsFriday5 series - today's contributor is Alan Shimel. He's DevOpstastic!
1) How would you describe the relationship between DevOps, Agile and ITIL?
In spite of some people thinking that ITIL and Agile have been somewhat of a failure or perhaps a better way of saying is “not as successful as they could have been”, I think we need to think of all of these IT methodologies and movements as a continuing evolution. I don’t think you could have a DevOps without first having Agile. The same goes for ITIL laying a foundation that later patterns such as DevOps built on. Even if it is learning from past mistakes, I think these things are evolutionary, not revolutionary.
2) Can you describe what DevOps looks like when it’s ‘done’?
Who said it was ever done? Seriously, I think DevOps is an ongoing process of constant improvement. There are always improvements to be made, lessons learned and continuous learning. However at some point you can look back and say we are operating at a much higher level now than we were at some point in the past and you can point to DevOps methodologies as being at least partly responsible for that. But I don’t think there is a “eureka” moment. I think it is something you recognize with hindsight. In the moment you are too involved in the here and now to take stock.
3) What do you think are the key metrics for DevOps?
I think every single business has to be measured on revenue, costs and profits. Customer satisfaction is another big one. I think the easy answer is how many deploys a day, how quick you develop. But I think that could be a red herring. Different parts of the IT machine move at different speeds and fast for one company is not fast for another. So I would say measuring deployments a day could be a false metric in some cases.
4) What attributes constitute a culture embracing DevOps?
No finger pointing, no prima donnas, recognizing that everyone’s contribution is important and that it is the total success of the team that determines our success. These are the cultural values I would look for.
5) Is Continuous Delivery the ultimate goal of DevOps? How do other ‘Continuouses’ (continuous deployment, testing, improvement etc) contribute in a DevOps transformation?
How do other 'Continuouses' (continuous deployment, testing, improvement etc) contribute in a DevOps transformation? CD has been called “the cure” for DevOps and it is a big part of showing DevOps is in place, but all of the “continuouses” including security are necessary to really have CD working correctly. So while it is a good “canary in the coal mine” it is not the be all and end all of DevOps.
About Alan: As Editor-in-chief of DevOps.com, Alan Shimel is attuned to the world of technology. Alan has founded and helped several technology ventures, including StillSecure, where he guided the company in bringing innovative and effective networking and security solutions to the marketplace. Shimel is an often-cited personality in the security and technology community and is a sought-after speaker at industry and government conferences and events. In addition to his writing on DevOps.com and Network World, his commentary about the state of technology is followed closely by many industry insiders via his blog and podcast, "Ashimmy, After All These Years". Alan has helped build several successful technology companies by combining a strong business background with a deep knowledge of technology. His legal background, long experience in the field, and New York street smarts combine to form a unique personality.
Do you have something you'd like to say about DevOps? If you would like to be featured on #DevOpsFriday5 click the button below.