Pragmatic DevOps: an introduction · agile software development agile infrastructure management it...

Post on 23-Jun-2020

6 views 0 download

Transcript of Pragmatic DevOps: an introduction · agile software development agile infrastructure management it...

Pragmatic DevOps:an introduction

KAIMAR KARUitSMF Hungary

November 16, 2018

@kaimarkaru

PRESENTER: KAIMAR KARU

Teaching and Professional Training

Project Management

IT Service Management

Appreciating good beer

Software Development

IT Operations and Support

2

itSMF

@kaimarkaru

CORRELATION AND CAUSATION

3

http://www.tylervigen.com/spurious-correlations

@kaimarkaru

HAWTHORNE EFFECT

4

IT IN THEENTERPRISE

@kaimarkaru

IT AND THE ENTERPRISE

$$

6

@kaimarkaru

CHANGING EXPECTATIONS

$

7

@kaimarkaru

THE CHANGING ROLE OF IT

PASSIVEORDER-TAKER

IT

„THE BUSINESS“REQU

IREMEN

TS SOLU

TIO

NS

THE ORGANISATION

ACTIVEBUSINESS ENABLER

IT

REQUIREMENTS SOLUTIONS

8

@kaimarkaru

TOWARDS BI-MODAL IT?

9

MODE 1SYSTEMS OF RECORD

MODE 2SYSTEMS OF INNOVATION

AND THEN THERE WASDEVOPS

@kaimarkaru

DEVOPS: THE THREE WAYS

11

https://itrevolution.com/the-three-ways-principles-underpinning-devops/

The First Way:Systems Thinking Dev Ops

Business Customer

Dev Ops

The Second Way:Amplify Feedback Loops

The Third Way:Culture Of Continual Experimentation And Learning Dev Ops

@kaimarkaru

DEVOPS: CALMS

CULTURE AUTOMATION LEAN MEASUREMENT SHARING

12

https://itrevolution.com/devops-culture-part-1/

@kaimarkaru

PSEUDO-DEVOPS

13

DevOps Team

ImplementingDevOps

‘Scientific’formulas of success

Implementing theSpotify model

DevOps Process

Big Bang DevOps

X-as-a-Silver-Bullet

DevOps is Tech

DevOpsQualifications

@kaimarkaru

AGILE

ITSM

THE ORIGINS OF DEVOPS

14

LEAN

@kaimarkaru

CLOUD COMPUTING

MAPPING THE DEVOPS MOVEMENT

15

AGILE SOFTWAREDEVELOPMENT

AGILE INFRASTRUCTUREMANAGEMENT

IT OPERATIONS MANAGEMENT (ITIL®)(IGNORING THE SERVICE VIEW)

WATERFALL PROJECT MANAGEMENT(USED FOR PROJECTS AND PRODUCTS)

TOYOTA PRODUCTION SYSTEM (LEAN)(WITH A LOT OF CARGO-CULTING)

VALUE STREAMMAPPING

DevOps

TOOLING

PRACTICES

PRINCIPLES

@kaimarkaru

IN A NUTSHELL (BUT THERE ARE MORE NUTS)

16

TOOLING

Infrastructure mgmt.ContainerizationVersion controlRelease mgmt.MonitoringApp. perf. mgmt.Workflow mgmt.Alerting

PRACTICES

MicroservicesServerlessWork visualizationCI/CD/CDDark releasesInstrumentationChaos engineeringExperimentation

PRINCIPLES

High availabilityHigh scalabilityAutomationCost != #1 concernInfrastructure as codeGraceful degradationAnti-fragilityCont. improvement

COMPLEXITY THINKING, EVOLUTION, AND CONTINUAL LEARNING

@kaimarkaru

EMPATHY AND COLLABORATION

17

@kaimarkaru

HOW IT WAS INTENDED TO BE

18

HR MGMT FIN

SALES DEV OPS

http://www.jedi.be/blog/2012/05/12/codifying-devops-area-practices/

DevOps – optimize the whole

Theory of Constraints

Business Customer

@kaimarkaru

WHAT REALLY HAPPENED

19

HR MGMT FIN

SALES DEV OPS

http://www.jedi.be/blog/2012/05/12/codifying-devops-area-practices/

DevOps – optimize the whole

Theory of Constraints

Business Customer

@kaimarkaru

(AVOIDING) LOCAL OPTIMIZATION

Dev OpsBiz Sec QA

BizDevSecQAOps, anyone?

20

@kaimarkaru

SERVICE EXPERIENCE

PRE-PURCHASE PRODUCT POST-PURCHASE

21

PRINCIPLESAND PRACTICES

@kaimarkaru

THE CYNEFIN FRAMEWORK

Fixed constraints

Governing constraints

No effectiveconstraints

Enabling constraints

Good practice

Best practiceNovel practice

Exaptive practice

Multiple answers tochoose from

One answer exists

Multiple (conflicting)coherent hypotheses

Actions required

OBVIOUS

DISORDER

COMPLICATED

CHAOTIC

COMPLEXSENSE-ANALYZE-RESPOND

SENSE-ANALYZE-RESPONDACT-SENSE-RESPOND

PROBE-SENSE-RESPOND

23

@kaimarkaru

TOYOTA PRODUCTION SYSTEM PRINCIPLE #1

24

Base your managementdecisions on a long term

philosophy, even at the expenseof short-term financial goals.

@kaimarkaru

LEAN PRINCIPLES

25

CUSTOMER VALUE VALUE STREAM FLOW PULL PERFECTION

@kaimarkaru

HOSHIN KANRI

26

» Step 1: Establish the organization’s vision» Step 2: Define strategic objectives (3-5 years)» Step 3: Define annual objectives» Step 4: Share specific, measurable objectives with the whole organization» Step 5: Execute the annual plans» Step 6: Monthly or quarterly reviews» Step 7: Annual review

P

DS

A

See also: Hoshin Kanri X Matrix

@kaimarkaru

TOYOTA (IMPROVEMENT) KATA

27

UNDERSTAND THEDIRECTION

GRASP THECURRENT

CONDITION

ESTABLISH THENEXT TARGETCONDITION

PDCA TOWARDTHE NEXT

TARGET CONDITION

1 2 3 4

CC

TC

Mike Rother, „Toyota Kata“: https://www.amazon.com/Toyota-Kata-Mike-Rother/dp/0070683468

@kaimarkaru

VALUE STREAM MAPPING (VSM)

28

» Process time: the actual time it takes to complete the work item» Lead time: the time from the work being made available to passing it on» Quality is measured by % Complete & Accurate (from the next step’s point of view)» Activity ratio: time used vs. time taken

ACTIVITY ACTIVITY ACTIVITY ACTIVITY ACTIVITY

2 days

10 days

5 days

14 days

5 days

60 days

2 days

90 days

1 day

I I I I

SOURCE OUTPUT

Daily Monthly

@kaimarkaru

WHAT AGILE IS ABOUT

Agile is not about failing fast,but about learning fast.

29

@kaimarkaru

VISIBILITY, SUSTAINABILITY, AND FLOW: KANBAN

30

MEASUREFLOW

LIMIT WIPVISUALIZEWORKFLOW

Utilizing a system to 100% of its capacity will lead to minimal throughput

@kaimarkaru

ITIL PRACTITIONER: 9 GUIDING PRINCIPLES

31

https://www.axelos.com/9-guiding-principles

DIGITALTRANSFORMATION

@kaimarkaru

DIGITAL TRANSFORMATION IN A NUTSHELL

» And pay attention to the following:» Focus on customer objectives (to co-create customer value)» Adopt a service mind-set» Challenge the status quo in the organizational» Rethink the role of leadership (order-givers vs. enablers)» Increase resilience to be able to learn from experiments» Streamline processes, procedures, and the use of data

» Apply methods and tools most suitable in the given context

33

Figure out how to leverage technologyto help the organization succeed.

@kaimarkaru

ORGANIZATIONAL BENEFITS

34

INCREASEDRESILIENCY

IMPROVEDCOLLABORATION

ENGAGEDEMPLOYEES

FASTERTIME-TO-MARKET

ABILITY TOINNOVATE

INCREASEDFLEXIBILITY

INCREASEDSECURITY

INCREASEDSTABILITY

@kaimarkaru

HOW TO BECOME BETTER AT THE THREE WAYS

35

BRING PAINFORWARD

USE SHAREDOBJECTIVES

OPTIMISE FORTHE WHOLE

MINIMIZEHANDOFFS

DISMANTLESILOS

SEPARATE PROJECTSFROM PRODUCTS

FIGHT FORTRANSPARENCY

CULTIVATE TRUSTAND RESPECT

@kaimarkaru

SOME INSPIRING QUOTES …

36

W. Edwards Deming

People are already doing their best;the problems are with the system.

Only management canchange the system.

@kaimarkaru

IMPACT ON ACCOUNTING PRACTICES

Dev OpsFin

37

No, FinDevOps is not really a thing.

@kaimarkaru

ADDITIONAL RECOMMENDED READING

38

USING KANBAN INIT OPERATIONS

ITIL AND DEVOPS:GETTING STARTED

@kaimarkaru

RECOMMENDED READING

39

Get in touch

@kaimarkaru

linkedin.com/in/kaimar

medium.com/@kaimarkaru