Ranger4 DevOps Blog

#DevOpsFriday5 with Kevina Finn-Braun

Posted by Priyanka Jain on Fri, Dec 11, 2015 @ 10:12 am

Find me on:

It's the Ranger4 #DevOpsFriday5 series - today's contributor is Kevina Finn-Braun. She's DevOpstastic!

1) How would you describe the relationship between DevOps, Agile and ITIL?

In many companies DevOps, Agile and ITIL are treated as separate disciplines, but by doing this we do ourselves and our customers a disservice. At their foundational levels DevOps, Agile and ITIL all share the same goals: continuous service delivery, service reliability and continuous service improvement.

2) Can you describe what DevOps looks like when it’s ‘done’?

DevOps isn't necessarily going to look the same at company A as it does at company B. There isn't a DevOps checklist that you can pull out and tick off all the boxes and once the boxes are all checked you're "doing devops". DevOps is about a company's culture, it's a way of behaving and working together towards the same goals whether you are in "ops" or in "dev"-it's about becoming a team and forgetting about silos.

3) What do you think are the key metrics for DevOps?

Change & Deployment Volume: this # should increase Percentage of Failed Deployment & Changes that cause customer impact: this # should decrease MTTR: I'm sure this is going to get some comments. However, IMO this number is about how well TEAMS work together when issues do occur and how quickly "dev" and "ops" work together to recover the service. # of Customer Tickets per incident: In the beginning this is going to show you which types of service disruptions or degradations affect your customers the most and where you should immediately harden your service. As teams start to work better together and are deploying more frequently with less customer impact this number combined with percentage of change/deployments that cause customer impact will let you know if you are achieving your goal. Availability: this is your "table stakes" measure-how available is your service?

4) What attributes constitute a culture embracing DevOps?

Inclusiveness Cooperation Relationships NOT Silos or departments, etc. "Service" NOT "Products"

5) Is Continuous Delivery the ultimate goal of DevOps? How do other ‘Continuouses’ (continuous deployment, testing, improvement etc) contribute in a DevOps transformation?

The ultimate goal of DevOps is "service reliability". "Service reliability" is achieved through continuous deployment, testing, improvement, etc. You achieve, continuous deployment, testing, improvement by changing the culture; the what, the how and the why. It's all a cycle.

 

About Kevina:

Kevina_Finn-Braun_1-1.jpg

Kevina Finn-Braun’s focus throughout her 18 years in the Internet Industry has been Operational Excellence and Risk Management. She is currently Director of Site Reliability Service Management at Salesforce where she leads the team focused on operational process improvements in the areas of incident, problem and change management. In her previous role as Director of Business Continuity at Yahoo! she led the team focused on risk management and service continuity best practices.

Follow Kevina: 

On Twitter
On LinkedIn

Do you have something you'd like to say about DevOps? If you would like to be featured on #DevOpsFriday5 click the button below.