Embedding Ownership: A DevOps Best Practice

from where i sit in the devops community, there is often more focus on dev than on ops. damon edwards (@damonedwards) of simplifyops sought to change that with his talk, ops happens : devops beyond deployment ,.

damon dove right into the primary, systemic force behind most devops problems - silos. the product development process goes like this: planning-->dev-->release-->operate. the problem is the tendency in many enterprises to place similar functions together. everyone ends up in a silo.  then walls build up between the silos.  eventually, people only know life in their silo, making handoffs even harder.

we often find application knowledge and business intent are heavily emphasized on development side but light on the operations side.  likewise, operational knowledge is heavy on the ops side, but light on the development side. furthermore, development has ownership but limited accountability, while operations has accountability but no ownership.

while many enterprises are striving towards building cross-functional teams, the reality is that the transformations often stop short of truly integrating operations. the result? silos remain.

so, one has to ask, why is this so hard?

the reality is that enterprise operations are under tremendous pressure.  one side is telling them to go faster and open it up and the other side is telling them to be more secure and be more reliable. these are often seen as competing priorities.

to solve this, enterprises need to “shift left” in the product development cycle operations activity as much as possible. they need to do as much as possible during development. for the deploy function, enterprises should be:

1. writing/running automated tests.
2. writing/exercising deploy automation.
3. running security scanning tools.

for the operate function, enterprises should be:

1. writing/exercising automated runbooks.
2. writing/exercising monitoring/metrics.
3. operational control (safely!).

however, shifting operations to the left is much harder. how do you do it? embed ownership.

let me repeat: embed ownership .

first, those who build something define the procedures to fix it, and those who build something fix it when it breaks.

that sounds simple, but raise questions:

1. how do you safely and securely give out access?
2. how do you enable the experts to contribute remediations?
3. how do you give the experts visibility into operations?
4. how do you do postmortems days/weeks/months later?

damon recommended four steps.

step 1- establish a secure ops portal

step 2- establish an sdlc for ops procedures

step 3- connect with enterprise management systems

step 4- make compliance really happy

ticketmaster is a real-life example of this working at a large, prominent scale. ticketmaster calls their system, “support at the edge” and it involves:

• automated ops procedures written/vetted by the delivery teams.
• ops remained in full control of what can run and security policy.
• empowered support teams with self-service ops tasks.
• empowered developers with limited self-service operations.
• combined with new incident response model.

ticketmaster has seen transformative results. before support at the edge, the average mean time to respond was 47 minutes. now, support at the edge has reduced that to just 3.8 minutes in addition to decreasing escalations 50% and overall support costs 55%.   ticketmaster has seen real results.

damon has more details in his talk, which you can watch online here. if you missed any of the other 30-minute long presentations from all day devops, they are easy to find and available free-of-charge.

finally, be sure to register you and the rest of your team for the 2017 all day devops conference. this year’s event will offer 96 practitioner-led sessions (no vendor pitches allowed). it’s all free, online on october 24th.