devops means effectiveness first
DESCRIPTION
talk presented at the DevOpsDays Berlin 2014. http://devopsdays.org/events/2014-berlin/ Twitter: @blndevops, #devopsdays #Berlin More details: http://bit.ly/1wvYV3x ABSTRACT: In this talk we explore in detail how efficiency and effectiveness are related to DevOps and the traditional separation of Development and Operations. Companies are usually aiming for high efficiency and predictability. This seems to make sense in the first place, as no one wants to be inefficient, right? But wait a second, the ask for efficiency might actually be a source for a permanent conflict with the DevOps idea. The focus on “synergy effects” and “good utilization” – which is a focus on efficiency – is often one of the main motivations for creating silos in the organisation, for the classical separation between Dev and Ops. Quite often those structures are neither effective nor efficient in the long run. On the other hand, with DevOps done right one can achieve a high level of effectiveness: Horizontal scaling, that is, increasing for a team their coverage of the value stream from idea to production, brings naturally the focus on doing the right thing for the customer. Furthermore, by improving the efficiency of an effective process, DevOps can enable companies to be ahead of their competitors. What I can learn in this session? * You can gain a better understanding how the DevOps approach yields to good organizational setups. * You learn some good arguments, why the traditional approach is suboptimal, and understand the mechanics that lead to ineffective and inefficient structures. * You learn good arguments for selling DevOps better * You learn ideas which help you to make the right choices in your DevOps journey.TRANSCRIPT
- 1. DEVOTPSDAYS are 09 Hlex Schvuarlz E Galexrchwarfzbln $ E alexanc| enschwarf1@here. com B e i n 2 0 1 4 E de. lin| :edin. comIinInlexanderxclnvuarfzberlin
- 2. we are hirin v Pllex Schwarfz u Calexschwarfzbln $ g a| exancler. schvuar+z@here. com m cle. |inkecIin. comIinlalexanderschvuarfzberlin
- 3. i"; irL[ATS iii. ms mu_i; ... = our = 5 ll? = console oi-: lpu: l code ldeeslreomtles -VJIMI Devops is smurf! -l; J!a' Clessicc-. I is cliiculff -! now to sell Devops beer? an , . i:1sL: -. ' : -. ;:J 9293.3.. . .
- 4. D . . F. J w VI Up to three jears ago. I Q, Q, I had no clue about the difference between efficient and effective. 3 I basicall1 used them as ssinonxims. Effectiveness is. .. the degree to which objectives are achieved. in contrast to efficiencj, effectiveness is determined without? reference to costs or costs, YQSOUYCES YQSOUYCQS
- 5. perfect spot but risks] Sweat spot EX/ ililA@lL. E Photographer produces @ cover picture for a magazine cg. .. . .;: ~ Iy - customer bus]: *5, A -number of pictures cover picture K -total time - readers like it -costs - good sales numbers
- 6. EX/ llllM'9. E fixing flat tire
- 7. EX/ llllAlPlLE Customer Support %? f_ i Q - customer ' satisfaction eg. Zappos - customer calls per hour - number of CS employees - waiting time
- 8. @EBR/ Mll@llll . sLn C 92" - Securitsg Clpg? Q - cjcle time for DEM " , - new features -fixing bugs - scaling upldown - new test env - happsi customers - success . Hvailabiliidi sf - number of people - number of server - costs
- 9. *I. ic: ssEcc. l approach "hlhefgj effects" "eztperts should do expert work" "'me: ti'mize u'ii| i2ction" "cost savings"
- 10. Classical Cllcl Devops approach on approach und rsta ed Qocs _J% g H -Flvailabi| it1,SLFl, Securitsg (L3 f M 1 approach mans; incider at the same time -c1cle time for -new features -fixing bugs vi) CT) -scaling upldown ( 3 - new test env -arch change " ou product does not have pYiDYH'' Scc Eng - itproducts _, _/) - technologies - = |*peop| e