XebiaLabs Enterprise DevOps

5 Lessons from Enterprise DevOps

Andrew Phillips

2

About me

▪ VP DevOps Strategy for XebiaLabs ▪ Been on both sides of the “Dev…Ops” fence ▪ Lots of enterprise soAware development on high-‐performance systems

▪ AcDve open source contributor and commiFer

▪ Regular meetup, conference etc. presenter Andrew Phillips

3

About me

4

Agenda

▪ DevOps vs. “Enterprise DevOps”

▪ 5 Lessons from Enterprise DevOps

▪ What Does This Look Like in PracDce?

▪ QuesDons

5

DevOps vs “Enterprise DevOps”

6


7


> US$1tn!

8


9


“Enterprise DevOps” = DevOps in complex and complicated environments

10


Different balance of AutomaDon, Visibility and Control

Control

Visibility

Automa1on

11



Control

Visibility

Automa1on

12



Control

Visibility

Automa1on

13

A Unified Theory of Enterprise DevOps

14

A Unified Theory of Enterprise DevOps

Just kidding

15

5 Lessons From Enterprise DevOps

16


1.  Top-‐down vs. boFom-‐up

17


1.  Top-‐down vs. boFom-‐up 2.  Cross-‐cu\ng concerns

18


1.  Top-‐down vs. boFom-‐up 2.  Cross-‐cu\ng concerns 3.  StandardizaDon

19


1.  Top-‐down vs. boFom-‐up 2.  Cross-‐cu\ng concerns 3.  StandardizaDon 4.  Dev(.+)Ops

20


1.  Top-‐down vs. boFom-‐up 2.  Cross-‐cu\ng concerns 3.  StandardizaDon 4.  Dev(.+)Ops 5.  Inward vs. outward

21


1.  Top-‐down vs. boFom-‐up 2.  Cross-‐cu\ng concerns 3.  StandardizaDon 4.  Dev(.+)Ops 5.  Inward vs. outward 6.   Means, not goals

22

V I S I B I L I T Y

AUTOMATION

CONTROL

§  ConDnuous Delivery and DevOps pioneer, authority and technology leader

§  Global team in US, Europe & APAC

§  Consistently recognized by leading industry analysts

ConnecDng the dots for ConDnuous Delivery at enterprise scale

About XebiaLabs

G l o b a l L e a d e r s D e l i v e r S o A w a r e w i t h X e b i a L a b s

23

VISIBILITY

CONTROL

AUTOMATION

Award-‐winning tools, recognized by leading industry analysts

XebiaLabs SoluPons: ConnecPng the dots for ConPnuous Delivery at enterprise scale

24

Top-‐down vs. boSom-‐up

25

26

27

28

29


30


31

Cross-‐cuTng concerns

32


Audit Security

ReporDng

Usability

33

StandardizaPon

34

StandardizaPon

35

StandardizaPon

36

StandardizaPon

37

StandardizaPon

hFp://mcfunley.com/choose-‐boring-‐technology

38

StandardizaPon

hFp://mcfunley.com/choose-‐boring-‐technology

39

Dev(.+)Ops

▪  QA ▪  Compliance ▪  Security ▪  Change & Release management ▪  Programme management

▪  …

40

Dev(.+)Ops

41

Dev(.+)Ops

42

Inward vs. outward

43

Where are the microservices???

Inward vs. outward

44

Inward vs. outward

Two disPnct types of DevOps/Agile/CD/etc. organizaPons

45

Inward vs. outward

Two disPnct types of DevOps/Agile/CD/etc. organizaPons ▪  Type 1: −  AutomaDon, automaDon, automaDon

46

Inward vs. outward

Two disPnct types of DevOps/Agile/CD/etc. organizaPons ▪  Type 1: −  AutomaDon, automaDon, automaDon

▪  Type 2: −  Agile, conDnuous delivery & small changes −  product teams & experimental organizaDons −  cultural responsibility shiA

47

Inward vs. outward

48

Inward vs. outward

49

Inward vs. outward

▪  Most enterprise success stories so far are type 1

▪  Most of the “unicorn” stories are type 2

▪  Moving to type 2 is significantly harder than implemenDng type 1

▪  Requires far more wide-‐reaching changes: org structure, company culture etc.

50

Inward vs. outward

•  Waterfall à agile: 3 years •  220 Apps -‐ 1 deployment per month •  “EVERY manual tester does automaDon” •  “We don’t log bugs. We fix them.”

•  Measures are built in & visible to everyone •  Promote your wins! Educate your peers.

•  EVERYONE can do conDnuous delivery.

51

Inward vs. outward

700 deployments / year

10 + deployments / day

50 – 60 deployments / day

Every 11.6 seconds

52

Means, not goals

"I need me some DevOps" ▪  CIO of major organizaDon: “What is DevOps and what do I need

to do about it? I’m concerned about missing the boat, but have no idea what DevOps means for my organizaDon”

▪  Lack of clear definiDon and overlapping markeDng messages create confusion

53

Means, not goals

▪  DevOps is a means, not a goal ▪  There is no “standard DevOps template” that to apply ▪  There are common elements to many of the DevOps success

stories that we can learn from

54

Means, not goals

▪  DevOps is a means, not a goal ▪  There is no “standard DevOps template” that to apply ▪  There are common elements to many of the DevOps success

stories that we can learn from

55

Means, not goals

56

Metrics, metrics, metrics

▪  “Concept-‐to-‐cash” Dme

▪  “Commit-‐to-‐cash” Dme

▪  # producDon deployments/Dme

▪  # producDon deployments rolled back/Dme

▪  MTTR

▪  Business value/Dme

▪  Developer feedback Dme

▪  Handover Dme during release

▪  Time spent providing audit data

57




▪  # producPon deployments/Pme

▪  # producPon deployments rolled back/Pme

▪  MTTR





58


▪  “Concept-‐to-‐cash” Pme




▪  MTTR

▪  Business value/Pme




59



▪  “Commit-‐to-‐cash” Pme



▪  MTTR


▪  Developer feedback Pme

▪  Handover Pme during release


60

What our users do…

StandardizaPon

Mobile app

Web frontend

Mainframe change

61



62


Dev(.+)Ops

63


Dev(.+)Ops

64


Inward vs. outward Review user behavior through UEM Data

65


Means, not goals

66

Example: Handover Pme

▪  Value-‐stream mapping −  Baseline data and progress measurement

▪  Restructuring teams −  IntegraDng QA and Development

▪  Self-‐service capability −  QA gets push-‐buFon loads

▪  AutomaDon −  Automated environment refresh

67

Example: Handover Pme

68

Example: Concept to cash Pme

▪  Code analysis & inspecDon −  Building a dependency graph

▪  Increase in test automaDon −  MiDgate risk of regression

▪  Shadow mode operaDon ▪  Rank by value −  Determine priority for investment

69

Example: Concept to cash Pme

70

Example: Time to provide audit data

▪  Changed communicaDon process and tooling −  No more requests for deployment by email

▪  Added regular data exports into a centralized audit database −  Had to change tooling to make that possible

▪  Added custom logging to automaDon tooling −  To allow for correlaDon of data

▪  Training & internal info material −  Explaining the requirements for audit data to the teams

71

Example: Time to provide audit data

72

A quick takeaway…

▪  “I am not a crusader for open source, I am a crusader for you building the best soAware possible, you shipping the best soAware to your customer possible, you having an awesome soAware development team.”

▪  “It’s not about open or closed source, it’s about what’s best for the end user, […] it’s about what’s the best for your business, your developers, your customers right now.”

73

A quick takeaway…

▪  “I am not a crusader for open source, I am a crusader for you building the best soAware possible, you shipping the best soAware to your customer possible, you having an awesome soAware development team.”

▪  “It’s not about open or closed source, it’s about what’s best for the end user, […] it’s about what’s the best for your business, your developers, your customers right now”

Chris Wanstrath, CEO at GitHub

hFps://a16z.com/2016/01/06/a16z-‐podcast-‐what-‐soAware-‐developers-‐and-‐therefore-‐every-‐company-‐need-‐2/

Resources

75

Resources

▪  Get Started with XebiaLabs www.xebialabs.com www.xebialabs.com/products blog.xebialabs.com @xebialabs

youtube.com/xebialabs

▪ The Periodic Table of DevOps hFps://xebialabs.com/periodic-‐table-‐of-‐devops-‐tools/

▪ eBook: The IT Manager’s Guide to CD hFps://xebialabs.com/resources/ whitepapers/the-‐it-‐managers-‐guide-‐to-‐ conDnuous-‐delivery/

76

Almost done!

77

V I S I B I L I T Y

AUTOMATION

CONTROL

Q & A

ConDnuous Delivery Resources

QuesPons?

www.XebiaLabs.com

78

Thank you

XebiaLabs Enterprise DevOps

Technology