It's the Ranger4 #DevOpsFriday5 series - today's contributor is Sebastian Spies. He's DevOpstastic!
1) How would you describe the relationship between DevOps, Agile and ITIL?
The relationship between DevOps, Agile and ITIL is similar to that of two people standing under an umbrella. The umbrella is DevOps, and one individual is Agile and the other is ITIL. The umbrella needs to be held up by the individuals, as well as it covers them both. This is how we view the relationship between these three items. DevOps is the overarching culture or philosophy of the organization, and Agile is the tool on the developer side, and ITIL is the tool on the operations side.
2) Can you describe what DevOps looks like when it’s ‘done’?
When DevOps is ‘done’, it looks like a relationship of collaboration and shared responsibility. Both parties, Dev and Ops, have an understanding of the tool chain. A tool chain that looks something like Eclipse>Jenkins>Docker, or input the specific tools of your organization. What occurs is no bottlenecks in responsibility, as well as the mindset is one of the team. For example, if a deployment fails, it is not the deployment manager's fault, but rather the DevOps team's fault.
3) What do you think are the key metrics for DevOps?
We are looking for two metrics. Minimizing the round trip time of user requirement to development to deployment, as well as minimizing the number of roundtrips needed. The lower both of these numbers are, the more effective our DevOps strategy, as well as the better our development process.
4) What attributes constitute a culture embracing DevOps?
In a culture of DevOps, we look for a team player. Also, a person needs to be able to share responsibilities, as well as take on the responsibilities of others, although these responsibilities are not specifically in their job description. The last essential characteristic is being able to see the perspective of other parties. Meaning, development needs to understand deployment and deployment needs to understand development.
5) Is Continuous Delivery the ultimate goal of DevOps? How do other ‘Continuouses’ (continuous deployment, testing, improvement etc) contribute in a DevOps transformation?
The simple answer is yes. The reason Continuous Delivery is the ultimate goal is to be able to meet the needs of the end user as they arise or are updated. ‘Continuous’ benefits the DevOps transformation because it provides the ability to update and satisfy needs as they arise, while putting a system in place which has the technical ability to make these changes. There is a concept of nothing is ever truly ‘finished’.
Sebastian Spies is the co-founder and CEO of Datapath.io and is a Border Gateway Protocol (BGP) expert. He has built the Datapath.io system to provide a network monitoring and traffic optimization solution, which allows for optimizing traffic for latency, bandwidth, and cost.
Do you have something you'd like to say about DevOps? If you would like to be featured on #DevOpsFriday5 click the button below.