Ttop 5 Myths of DevOps - Karen Chua

Pink Elephant – Knowledge Translated Into Results

Top 5 Myths of DevOps

Karen Chua Management Consultant

Pink Elephant

Top 5 Myths of DevOps © Pink Elephant, 2016. All Rights Reserved.

Welcome & Agenda

1.  Introduction: Why DevOps?

2.  What is DevOps?

3.  Top 5 Myths of DevOps

4.  Keep CALMS

2

OpsDev


Business Perspective: Our Cadence Is Off

Historically…

TheBusiness Dev Ops

Cadence–TheFloworRhythmofEvents.

WaterfallProjects

X

X XX X

X

RigorousProcesses

X

X

InnovaDon

3


Impacts On The Business

§  Slow business responsiveness §  Customer dissatisfaction §  Poor customer experience §  Reduced ability to compete §  Wasted resources §  Lost productivity §  High costs and risks

h"p://marke+ngevolu+on.wordpress.com/

4


Better, But Not Quite There

Agileandleandevelopmentprac5cesspeedthingsup,but....

TheBusiness Dev Ops

Agile/LeanDev

X

XX

XX

X

RigorousProcessesInnovaDon

XXX

X

X

XX

XX

XX

XX

XX

5


DevOps Improves Our Cadence

…agileandleanservicemanagementprac5cesarealsoneeded.

TheBusiness Agile/LeanDevOps

ConDnuousDelivery

X

X XX

X

WinningThroughInnovaDon

XX

X

X

XX

XX

XXXX

XXX

X

X

X

XX

XX

X X

6


Isn’t This How It’s Supposed To Be?

Dev

Ops Biz

DevOps

Speed–Produc5vity–Quality

7


IT Perspective: The Wall Of Confusion

DevwantsCHANGE OpswantsSTABILITYWALLOFCONFUSION

8

§  Not developed fast enough – low deployment frequency

§  Do not meet the business outcomes

§  Unable to support the applications effectively

§  Do not meet the business value


Finding The Balance

Whatarethedangers? ExtremeFocusonStability

ExtremeFocus

onChange

What does the business want? All of the above

9


What Is DevOps?

§  Responds to accelerated demand for quality software products and services

§  Acknowledges the interdependence of IT functions

§  Recognizes the need for cultural improvements

§  Supports and leverages agile, lean and IT service management (ITSM) practices

§  Encourages the use of automation

DevOps is a cultural and professional movement that stresses communication, collaboration and integration between software developers and IT operations professionals.

10


DevOps Goals

§  Better align IT responsiveness and capabilities to business needs

§  Produce smaller, more frequent software releases

§  Reduce effort and risks associated with software development, transition and operation

§  Improve time to market

§  Improve quality of code §  Improve quality of software

deployments §  Reduce cost of product iterations

and delays §  Instill a culture of communication

and collaboration §  Improve productivity §  Improve visibility into IT

requirements and processes

11


The Three Ways

§  The First Way – Flow §  Understand and increase the flow of work (left to right)

§  The Second Way – Feedback §  Create short feedback loops that enable continuous

improvement (right to left) §  The Third Way – Continuous Experimentation &

Learning §  Create a culture that fosters:

§  Experimentation, taking risks and learning from failure

§  Understanding that repetition and practice is the prerequisite to mastery

12


Top 5 Myths Of DevOps

13

• DevOpsClasheswithITILMyth1:

• DevOpsDerailsSecurity&StabilityMyth2:

• DevOpsisallaboutAutoma+onMyth3:

• DevOpsTeamsmustbeCreatedMyth4:

• DevOpsisallaboutCultureMyth5:


“ItismyfirmbeliefthatITSMandtheDevOpsmovementarenotatodds.Quitetothecontrary,they’reaperfectculturalmatch.”

GeneKimAuthorofThePhoenixProject

14

Myth 1: DevOps Clashes With ITSM


DevOps & ITSM

§  ITIL encourages organizations to continuously adapt processes to current business needs

§  Apply agile, lean and DevOps principles over a foundation of ITIL best practice

§  ITSM processes are essential to ongoing operations, continual improvement and value creation

§  DevOps needs ITSM best practices to meet the goal of deploying faster changes without causing disruption

§  The integration of DevOps and ITSM helps to identify, reduce and eliminate ongoing risks and constraints

Repeatableservicemanagementprocessescanleadthewaytostablecon5nuousdeliveryandincreasedflow.

15


Truth 1: ITSM Processes Enable DevOps

§  Change Management §  Release & Deployment

Management §  Service Asset & Configuration

Management

§  Event Management §  Incident Management §  Problem Management §  Knowledge Management

AllITSMprocesseswillul5matelyplayaroleinsuppor5ngDevOpsbyincreasingflow,reducingconstraintsandcrea5ngbusinessvalue.

ITSM

KeyITSMprocessesthathelpenableDevOpsinclude:

16


CommonPracDces DevOpsPracDces

Errorsreportedlateinthedevelopmentcycleorbyusers

-  Aimforqualityatthesource-  Setthresholds-  Establishproac+vemonitoring

Opsfeelsthepain -  Devownsthequalityoftheircode-  DevprovidesLevel3support-  DevandOpsworktogetherin

cross-func+onalteamsInefficientescalaDonpracDces -  Clarifyroles,responsibili+es,

accountabili+es(ownership)-  Iden+fyandexploitbo"lenecks-  Improvefeedbackloops

DevOps Improves Incident Management

17



ViewedasreacDve -  Engageearlierinlifecycle.

Notactedupon -  Captureknowledge(knownerrors)assoonasitmakessensetodoso

-  Makechangesasneededtopreventproblemswhenjus+fied.

PerceivedasslowingDevdown -  Proac+velyiden+fyproblems

Viewedasbrainstorming -  Learnandprac+ceproventechniques

DevOps Improves Problem Management

18


DevOps Improves Change Management


Viewedasabarrier/boVleneck

-Viewasawaytomi+gaterisk

Processisn’ttriggered/stakeholdersaren’tengagedearlyenough

-  Increaseproac+vecollabora+onbetweenstakeholders

ChangeAdvisoryBoard(CAB)mustapprovetoomanychanges

-  Increasepercentageofstandardchanges-  Increasenumberofautomatedapprovals

(e.g.,ifitintegratesandpassestests,itisapproved)

Findtheguiltypartyorcoverupmistakeswhenthingsgowrong

-  Capture–inablamelessway–andactonlessonslearned

-  UseProblemManagementwhereneeded

19



Delaysbecauseenvironmentsaren’tready

-  Cross-func+onalteams–getOpsinvolvedearly–workinparallel

-  Automatetheprovisioningandsynchroniza+onofallenvironments

-  Self-serviceenvironmentcrea+on.Schedulingdelayscausedbyconflicts -  Con+nuousintegra+on

-  Automatedtes+ng

Deploymentdelays -  Planthereleaseinparallelwithdevelopment

-  Automateddeployment.Recurringproblems -  Shortenfeedbackloopsby

releasingmorefrequently

DevOps Improves Release & Deployment Management

20


Myth 2: DevOps Derails Security & Stability

§  Rapid deployments throws all risk management practices into the wind

§  Going faster can sometimes result in a reduction in quality The Truth is… §  Organizations that adopt DevOps practices can both go fast and

achieve more reliable services §  Efforts to capture quality at the source and ensure that errors are

not passed downstream §  Accomplished via practices such as version control, continuous

integration, continuous delivery and automated testing

21

Example:Googledoesabout5,500codecommitsperday,theyhaveabout15,000

so]wareengineers,and75millionhoursoftes+ngisruneachday.


Truth 2: DevOps Increases Agility & Stability

1.  Organizations are more agile: §  Code is shipped 30 times faster §  Deployments are completed 8000 times

faster

Source:2013StateofDevOpsReport–PuppetLabsandITRevolu+onPress

2.  Services are more reliable: §  There are 50% fewer failures §  Service is restored 12 times faster

Organiza5onsthatimplementedDevOpsprac5ceswereuptofive5mesmorelikelytobehighperforming.Why?

22


Increasing Agility

DevOps increases agility by: §  Breaking down silos §  Improving constraints §  Taking a unified approach to systems

engineering §  Applying agile principles to both Dev

and Ops §  Sharing knowledge, skills, experience

and data §  Recognizing the criticality of

automation §  Deploying faster with fewer errors

DevOpsextendsagileprinciplesbeyondtheboundariesofthesoQwaretotheen5redeliveredservice.

23


Myth 3: DevOps Is All About Automation

AutomaDonenablesagility,consistency,speedandreliability.

andmanymore…

Sharedaccesstoautomatedtes5ng,deployment,monitoringandITSMtoolsstreamlinessoQwaredeliveryandpreparesOpsforthelongrun.

24


Truth 3: Automation Enables DevOps

Enablers: §  Treating infrastructure as code (i.e.,

programmatically provisioning and managing infrastructure resources)

§  Repeatable and reliable deployment processes §  Continuous integration, continuous

delivery and continuous deployment

§  Development and testing (preferably automated testing) performed against production-like systems

§  On-demand creation of development, test, staging and production environments

§  Proactive monitoring of infrastructure components, environments, systems and services

25

Benefits: §  Faster lead times §  More frequent releases §  Less turbulent releases §  Fewer errors §  Higher quality §  Faster recovery §  Business and customer

satisfaction

Truth3:DevOpsisnotjustabout

automa5onbuttherearecommonenabling

prac5ces.


Myth 4: DevOps Teams Must Be Created

26

16%of2014surveyrespondentshadorwerecrea5ngDevOpsdepartments.Theseweremostly

departmentswith20-499employeesbutthetrendisgrowing.

Source:2014StateofDevOpsReport–PuppetLabs,ITRevolu+onPressandThoughtWorks


The Trend To Create DevOps Teams

§  There has been a dramatic increase in the creation of DevOps departments or teams that: §  Have Dev and Ops report to same management §  Build on an agile small team approach §  Are successfully applying DevOps principles

§  The pros and cons of this approach are not clear §  Are they doing anything noticeably different than

other IT departments?

27


The Downsides Of DevOps Teams

§  Yet another silo

§  Dev and Ops wash their hands of accountability

DevOpsac5vi5esbecome‘someoneelse’sproblem.’

28


DevOps Organizational Structures

Some organisations are: §  Assigning Ops liaisons to each Dev team §  Creating cross-functional product (vs. project)

teams to facilitate greater collaboration §  Adopting matrix or market-oriented structures (vs.

function-oriented structures) §  Creating shared services within Ops that Dev teams

can use to improve productivity

29


What Is A DevOps Engineer?

§  There is currently no ‘industry recognized’ job description or formal career track for a DevOps Engineer

§  Individuals filling these roles may be: §  Developers interested in deployment §  System Administrators who enjoy scripting and

coding §  General characteristics include someone who:

§  Wants to contribute his or her technical talent to business and process improvement initiatives

§  Is comfortable collaborating with others §  Wants to be in a workplace that promotes a shared

culture

30


Truth 4: Cross-Functional Teams

31

“The DevOps movement addresses the dysfunction that results from organisations composed of functional silos. This, creating another functional silo that sits between dev and ops, is clearly a poor (and ironic) way to try and solve these problems. DevOps proposes instead strategies to create better collaboration between functional silos, or doing away with the functional silos altogether and creating cross-functional teams (or combination of these approaches).”

Jez Humble (http://continuousdelivery.com/2012/10/theres-no-such-thing-as-a-devops-team/)


§  Culture is shown in: §  The way an organisation conducts business §  How an organisation treats its employees, customers and the

wider community §  The freedoms allowed in decision making, developing new

ideas and personal expression §  How power and information flow through the organisation’s

hierarchy §  How committed employees are towards collective objectives

32

Myth 5: DevOps Is All About Culture

Organisational culture is the behavior of humans within an organisation and the meaning people attach to those behaviors -

includes the organization's vision, values, norms, systems, symbols, language, assumptions, beliefs and habits.

Simplyput,cultureis‘thewaywedothings.’


Cultural Debt

§  Occurs when cultural considerations are disregarded or deferred in favor of growth and innovation

§  Hinders IT’s ability to progress because of: §  Extensive silos §  Workflow constraints §  Insufficient collaboration §  Miscommunications §  Project delays §  Waste §  Additional cost

DevOpspaysdownculturaldebtbyfocusingoncrea5ngatrustrela5onshipthatincludeshumanandtechnicalinterac5ons.

33


IT Is A Multicultural Society…

ITIL® is a registered trade mark of AXELOS Limited.

34


Characteristics Of A DevOps Culture

§  Shared vision, goals and incentives

§  Open, honest, two-way communication

§  Collaboration §  Pride of workmanship §  Respect §  Trust §  Transparency

§  Continuous improvement §  Experimentation §  Intelligent risk taking §  Learning §  Practicing

§  Data-driven §  Safe §  Reflection §  Recognition

Organiza5onalcultureisoneofthestrongestpredictorsofbothITperformanceandoverallperformanceoftheorganiza5on.

35


Shifting Thoughts & Behaviors

From §  IT focus (inside-out) §  Silos §  Command and control §  Task-oriented §  Blame §  Reactive §  Content §  Resistant §  Low trust

To §  Customer focus (outside-in) §  Cross-functional teams §  Collaborative §  Outcome-oriented §  Responsibility §  Proactive §  Courageous §  Flexible §  High trust

Realculturechangetakes5me.Itmustbeincrementalandperformedatarealis5cpace.

36


High Trust Vs. Low Trust

High Trust

Speed

Cost

Low Trust

Speed

Cost

37


DevOps & The Learning Culture

To make learning a part of the organisation’s culture: §  Incorporate learning into processes §  Encourage daily learning and knowledge

sharing §  Use technology to accelerate learning §  Make work educational

§  Experimentation §  Problem solving §  Demonstrations

§  Allow and use mistakes as sources of learning §  Make the results of learning visible

Tocreatealearningculture,leadersandmanagersmustvaluelearningandmodelthebehavior.

38


Truth 5: DevOps Is All About People

§  The way they think §  The way they interact §  The way they behave §  The way they work §  The way they perceive

themselves and their colleagues

Peoplewilladapttothevaluesandprac5cesofyourorganisa5onalculture.

39


“Anorganiza5on’sabilitytolearn,andtranslatethatlearningintoac5onrapidly,isthegreatestcompe55veadvantage.”

JackWelsh

40


DevOps Values

C.A.L.M.S C – Culture A – Automation L – Lean M – Measurement S – Sharing

41


Thank You. Questions?

Thank You!

Karen Chua

[email protected]

@karenchuakc

sg.linkedin.com/in/karenchua

www.pinkelephant.com

42

Date post:	16-Apr-2017
Category:	Technology
Upload:	pink-elephant
View:	160 times
Download:	0 times

Ttop 5 Myths of DevOps - Karen Chua

Technology