devops - why should we care?

62
1 DEVOPS – WHY SHOULD WE CARE? OCTOBER 5, 2015 / EMEA POWER HOURS / STEFAN ZUEGER, SWITZERLAND

Upload: stefan-zueger

Post on 23-Jan-2017

202 views

Category:

Leadership & Management


0 download

TRANSCRIPT

Page 1: DevOps - Why Should We Care?

1

DEVOPS – WHY SHOULD WE CARE?OCTOBER 5, 2015 / EMEA POWER HOURS / STEFAN ZUEGER, SWITZERLAND

Page 2: DevOps - Why Should We Care?

22

2 minutesWelcome to my DevOps

Supersummary

If everything seems under control, you're not going fast enough.Mario Andrettiracing legend* 1940

Page 3: DevOps - Why Should We Care?

33

Placing a new offering on the market first is often the only way to generate margin. Before competition picks up.

Page 4: DevOps - Why Should We Care?

44

In today’s digital economy, new offerings are made possible or strongly supported through software.

Page 5: DevOps - Why Should We Care?

55

DevOps is about getting new code to the market as fast as possible.

Page 6: DevOps - Why Should We Care?

66

It is not a technology, it is a cultural mindshift, bringing Dev, QA and Ops very closely together.

Page 7: DevOps - Why Should We Care?

77

However, certain technologies and practices can be used to accelerate this process.

automateintegrate

scale-outself service

capacity on demand

Page 8: DevOps - Why Should We Care?
Page 9: DevOps - Why Should We Care?

9

One of the most influental contributions to the SW-defined economy was published by Netscape-Founder Marc Andreesen four years ago, in August 2011

9http://www.wsj.com/articles/SB10001424053111903480904576512250915629460

Page 10: DevOps - Why Should We Care?

10

In it, he demonstrated the growing influence and value of SW-based companies in the global economy: Amazon, Netflix, Spotify, Skype, Google, LinkedIn

10http://www.wsj.com/articles/SB10001424053111903480904576512250915629460

Page 11: DevOps - Why Should We Care?

11

And he probably was right: Judging by the usage of social media services alone, we are looking at• 1.9 B users today• 2.1 B in 2016• 2.5 B in 2018

2.5 B are a third of the Earth’s population

11http://www.statista.com

WhatsApp900M users100% mobile

Facebook1.5B users78% mobile

Twitter304M users60% mobile

Spotify75M users15M subscribers15% mobile

Instagram310M users60% mobile

Page 12: DevOps - Why Should We Care?

12

New and existing companies choose software to disrupt the traditional way of doing business

• Either by enhancing the possibilities of traditional offerings

• Or by entirely substituting them

12

Page 13: DevOps - Why Should We Care?

13

Uber.com combines two features of the new, SW-enabled economy:

• It is easy to do business with – trough easy-to-use software

• Its services are provided by a crowd of individual contributors

13

Page 14: DevOps - Why Should We Care?

14

In December 2014, Web Strategist Jeremiah Owyang presents V2 of his “Collaborative Economy Honeycomb”

Topic: The disruption of twelve industries by peer2peer business models – powered by Software

14http://www.web-strategist.com/blog/2014/12/07/collaborative-economy-honeycomb-2-watch-it-grow/

Page 15: DevOps - Why Should We Care?

15© Copyright 2015 EMC Corporation. All rights reserved.

What do 2.5B users collaborating on a global scale expect from the services they use?

15https://www.emc.com/information-generation/index.htm

Faster Access to Services55%

Always Access to Services53%

Access from any Device50%

Personalized Experiences47%

Page 16: DevOps - Why Should We Care?

16© Copyright 2015 EMC Corporation. All rights reserved.

And what capabilities does a business need to develop to remain successful?

16https://www.emc.com/information-generation/index.htm

Predictively spot new opportunities60%

Demonstrate transparency & trust56%

Innovate in an agile way55%

Deliver a unique & personalized experience

45%

Always on, operating inreal time

38%

Page 17: DevOps - Why Should We Care?

17

Predictively spot new opportunities

Innovate in an agile way

Demonstrate transparency and trust

Deliver a unique and personalized experience

Always on, operating in real time

12%

9%

14%

11%

12%

How well prepared are businesses for the challenges of the future?

17https://www.emc.com/information-generation/index.htm

Page 18: DevOps - Why Should We Care?

1818

Innovate in an agile way 9%

89% of the Fortune 500 companies from 1955 do not exist today.

http://www.aei.org/publication/fortune-500-firms-in-1955-vs-2014-89-are-gone-and-were-all-better-off-because-of-that-dynamic-creative-destruction/

Page 19: DevOps - Why Should We Care?

1919

Innovate in an agile way 9%

This is where DevOps kicks in.

Page 20: DevOps - Why Should We Care?

2020

DevOps is not a technology.

DevOps is a cultural and operational model that fosters collaboration to enable high-performance IT to achieve business goals.

Page 21: DevOps - Why Should We Care?

2121

DevOps is not a technology.

It’s the principles of agile development applied to the entire IT lifecycle.http://www.agilealliance.org/the-alliance/the-agile-manifesto/

And smart technology can help DevOps.

Page 22: DevOps - Why Should We Care?

2222

So are we to become anarchists?

http://www.agilealliance.org/the-alliance/the-agile-manifesto/

Page 23: DevOps - Why Should We Care?

2323

And blow up all the structures we have become fond of?

Such as ITIL, (IT Infrastructure Library), the gold standard to organize IT operations in Enterprise environments?

Page 24: DevOps - Why Should We Care?

2424

Well,kind of.

Page 25: DevOps - Why Should We Care?

2525

DevOps constitutes a mindshift in understanding how Dev and Ops collaborate.

IT Production

StaticStable

Change-resistantLong-term

in defense mode

Page 26: DevOps - Why Should We Care?

2626

Dev, QA and Ops are understood as equal members of a production line, delivering a product to the consumer.ConsumersDev QA Ops

Product

Page 27: DevOps - Why Should We Care?

27http://www.bloorresearch.com/analysis/devops-itil-ibm-innovate/ 27

Keep the concept, drop the practice.if you separate out the

logical model of ITIL from the physical “best” practices (...) beneath it, ITIL is a valuable resource

Page 28: DevOps - Why Should We Care?

2828

DevOps is not about application performance.

Page 29: DevOps - Why Should We Care?

2929

DevOps is not about application performance.

DevOps is about bringing SW-based services to the market fast and in a good quality.

Page 30: DevOps - Why Should We Care?

3030

Developers know, what Operations need.

They should use Puppet to do configuration management and automate their Datacenter.

We’ll write our deployment scripts in Ruby so Operations can read what we are doing.

Page 31: DevOps - Why Should We Care?

3131

Operations know, what Developers need.

They want push button environments.

We need a system to replace all systems.

Page 32: DevOps - Why Should We Care?

3232

Devops is not about…

Tools

Automation

Root Rights

Silos

Page 33: DevOps - Why Should We Care?

3333

Devops is about…

Communication

Understanding

Integration

Relationships

Page 34: DevOps - Why Should We Care?

3434

DevOps focusses on...

Feedback

Collaboration

Continuous Improvement

Plan

Do

Act

Check

Page 35: DevOps - Why Should We Care?

3535

Timewarp!

Page 36: DevOps - Why Should We Care?

3636

Back in the 1940s, Toyota examined ways to improve productivity

Legend has it they found the solution when visiting a supermarket

Taiichi Ohno

Eiji Toyoda

大野耐 豊田 英二

Page 37: DevOps - Why Should We Care?

3737

In a supermarket, the customer determines the speed of the replenishining process by purchasing a product.

Not the Vendor.

Page 38: DevOps - Why Should We Care?

3838

They devised a production flow methodologyfocusing on the elimination of waste.

The Toyota Production System.

The Seven Wastes.

Page 39: DevOps - Why Should We Care?

39

The Seven Wastes.

39

They devised a production flow methodologyfocusing on the elimination of waste.

The Toyota Production System.

overproduction

waiting

transporting

excess inventory

movement

defects

overprocessing

Page 40: DevOps - Why Should We Care?

4040

lean manufacturing

The Toyota Production System.

Page 41: DevOps - Why Should We Care?

4141

lean manufacturing

Focus on Througput

Page 42: DevOps - Why Should We Care?

4242

lean manufacturing

Focus on Quality

Page 43: DevOps - Why Should We Care?

43

The Seven Wastes.

43

What does this mean for delivering an IT-enabled business service?

overproduction

waiting

transporting

excess inventory

movement

defects

overprocessing

Page 44: DevOps - Why Should We Care?

4444

What does this mean for delivering an IT-enabled business service?

transporting

Deploying systems into production manually is error-prone.

Page 45: DevOps - Why Should We Care?

4545

What does this mean for delivering an IT-enabled business service?

waiting

Delays because platforms are not ready kills productivity.

Page 46: DevOps - Why Should We Care?

4646

What does this mean for delivering an IT-enabled business service?

excess inventory

Purchasing capacity now and use it in three years is poison for any business case.

Page 47: DevOps - Why Should We Care?

4747

What does this mean for delivering an IT-enabled business service?

movement

Manual labor creates delays and errors.

Automate as much as you can.

Page 48: DevOps - Why Should We Care?

4848

Ok. Got it.

But how?

Page 49: DevOps - Why Should We Care?

4949

Forgetdepartments. They are silos.

Think workstreams.Think Pipeline

to Production.

Page 50: DevOps - Why Should We Care?

5050

No man is an island.

(No woman either.)

Try Pair Programming.

Page 51: DevOps - Why Should We Care?

5151

What did I accomplish yesterday?

What will I do today?

What obstacles are impeding my progress?

Run Daily Standup Meetings.

Page 52: DevOps - Why Should We Care?

5252

Increase competence by shifting experience.

Move in and out of comfort zones.Do Weekly

Rotations.

Page 53: DevOps - Why Should We Care?

5353

Every employee has the right to stop the process if she/he perceives quality issues.Encourage

Feedback.

Page 54: DevOps - Why Should We Care?

5454

Automate processes to reduce human error or to speed up process delivery.Automate.

Page 55: DevOps - Why Should We Care?

5555

Sell the vision, win the sale.Ask before

you sell.

Page 56: DevOps - Why Should We Care?

5656

Everything you wanted to know about Software

Why are your customers buying from you?

Which are your true differentiators from your competition?

How many of those differentiating aspects can be attributed to

functionality provided by software?

Do you have any plans for new, innovative offerings

based on software?

Page 57: DevOps - Why Should We Care?

5757

Everything you wanted to know about Accounta-bility

Who provides Quality Assurance?

Who develops and maintains the SW code for those differentiators?

Who operates your code?

Page 58: DevOps - Why Should We Care?

5858

Everything you wanted to know about Methodo-logies

What environments are your developers working with?

What methodologies are you actively promoting?

How similar / different are your production from your development

environments?

What rules do you need to comply with when testing code a) with synthetic data /

with customer data?

Page 59: DevOps - Why Should We Care?

5959

Everything you wanted to know about Change Rate

How often do you bring new releases into production?

Why (only) so few? Would doubling your release frequency interest you?

Why?

What is currently preventing an increase of release frequency?

Page 60: DevOps - Why Should We Care?

6060

Want to learn more?

Page 61: DevOps - Why Should We Care?

6161

Stef

an Z

uege

r+4

1 79

601

62

36st

efan

.zueg

er@

emc.

com

@SD

Zueg

er

Thank you!

Page 62: DevOps - Why Should We Care?