solve everyday it problems with devops

K3 Keynote 11/17/2016 8:30:00 AM

Solve Everyday IT Problems with DevOps

Presented by:

Sherry Chang

Intel

Brought to you by:

350 Corporate Way, Suite 400, Orange Park, FL 32073

888-‐268-‐8770 ·∙ 904-‐278-‐0524 - [email protected] - http://www.stareast.techwell.com/

mailto:[email protected]

http://www.stareast.techwell.com/

Sherry Chang Intel

Chief architect for Intel IT's DevOps initiative, Sherry Chang leads the DevOps Community of Practice. She is entrenched in coaching and leading Intel CIO’s mandated DevOps transformation effort. Involved in software development for more than twenty years, Sherry’s professional interests include software patents, test-driven development, continuous delivery, and infrastructure as code. She is a certified ScrumMaster and has eight software patents filed with Intel.

11/3/2016

1

How to Solve Everyday IT

Sherry ChangNovember 17, 2016

How to Solve Everyday IT

Problems with DevOps

,

Legal Notices

Some data was estimated at time of publishing.

Intel, the Intel logo, Intel Core, Intel vPro, Ultrabook, and Xeon are trademarks of Intel Corporation in the U.S. and other countries.

* Other names and brands may be claimed as the property of others.

Copyright 2016, Intel Corporation. All rights reserved. Please Recycle. Printed in the USA. 0113/KAR/KC/BP/5k 311133-008US

11/3/2016

2

About Me

BiographySherry Chang

Chief Architect of DevOps & Continuous Delivery

• @Intel Information Technology

• Focusing on CIO Mandated DevOps Transformation

20+ Years in Software Development

University of Texas at AustinUniversity of Texas at Austin

• BBA, Management Information Systems

3

sherrychangca

linkedin.com/in/sherryschang

What is DevOps?

DevDev OpsOps

4

11/3/2016

3

Typical Reactions

I don’t understand.How does this apply to me?This is too complicated.I am already too busy.Do we really want to deployDo we really want to deploy that often?

5

But The Pain is RealProject Deadline Pressure

Incidents Technical Debt

Deployment Pain

Fragile Code

DowntimeAngry Customers

Defects

Unplanned Work

Fragile Infrastructure

11/3/2016

4

What Good Looks Like

Zero Downtime (Planned or Unplanned)

Zero Defects

Automated Recovery

One Click Release

7

One Click Release

No Weekend or After Hour Releases

whatweput up withputupwith

weendupwith

8

~ astinM ippK

p

11/3/2016

5

Relief is available if you want it

Continuous DeliveryDeployment Pain

Project Deadline Pressure

Pain Remedy

Continuous Integration

Codified Infrastructure + Proactive Monitoring


Fragile Code

Fragile Infrastructure

Downtime

Reactive Fire FightingReactive Fire Fighting

Angry Customers

Recommendation

Accelerate

Continuously ImproveStart Small

10

Start Small

11/3/2016

6

If your Pain is.. Remedy is..y y


Fragile Code

Unplanned Work

Defects

11

Incidents


Team Commits To Trunk Every Day

Every Commit Should Automatically BuildEvery Commit Should Automatically Build Trunk on an Integration Machine

Automated Tests Validate Build

Team Commits to Keeping Build Green

12

11/3/2016

7

“Cease dependence on inspection to achieve quality Eliminate the need forachieve quality. Eliminate the need for inspection… by building quality into the product in the first place.”

13

~ W. Edward Deming

458

0.777292576 0.803370787

0.901639344

0 8

0.9

1

400

450

500

DRE = Defect Removal Efficiency

DRE Line

Intel Project with Continuous Integration

87

169168

102

336

178

0.5

0.7772925760.765432099

0.3

0.4

0.5

0.6

0.7

0.8

150

200

250

300

350

400

Q3 2011

43

8766

18 11

64 5435 3332

46

15 5 429

54

8 4 7

3519

6

8161

0

0.1

0.2

0

50

100

4.0 4.1.0 4.2.0 4.2.1 4.2.2

Development Internal QA External QA Customer Integration/Pilot Production Grand Total DRE

11/3/2016

8

458

0.777292576 0.803370787

0.901639344

0 8

0.9

1

400

450

500

DRE = Defect Removal Efficiency

DRE Line

Intel Project with Continuous Integration

87

169168

102

336

178

0.5

0.7772925760.765432099

0.3

0.4

0.5

0.6

0.7

0.8

150

200

250

300

350

400

CI Net Effect1. Defects are Discovered Earlier2. Defects Disappear Over Time

Q3 2011

43

8766

18 11

64 5435 3332

46

15 5 429

54

8 4 7

3519

6

8161

0

0.1

0.2

0

50

100

4.0 4.1.0 4.2.0 4.2.1 4.2.2

Development Internal QA External QA Customer Integration/Pilot Production Grand Total DRE

Recommendation

AccelerateAccelerate


Pay Attention to Early Indicators• % of Code Coverage & Build Failure

Green = Automated Build + Incrementally Increasing Code Coverage + Code Analysis

Green = Automated Build + 1 Test

16

• % of Code Coverage & Build Failure Rate (Effectiveness in getting defects out of system)

• Complexity Index (Amount of Technical Debt)

11/3/2016

9


Continuous Delivery

Deployment Pain


17

Continuous Delivery

Trunk is always 1 click away from deployment to production

Frequently delivering features in smallFrequently delivering features in small batches

Making flow of work thru delivery process visible

Actively seeking and implementing customer feedback

18

11/3/2016

10

Rapid Feedback Loop

Why It Works?

Decrease Cost of “Bet”

D l D l t f

19

Decouple Deployment from Business Decision

Recommendation



Pay Attention to:• Cycle Time

1. Automate, eliminate, or combine tasks to increase flow

2. Amplify feedback loop

Start with Value Stream Analysis

20

Cycle Time• Lead Time• Deployment Frequency

Stream Analysis

11/3/2016

11

New Feature Requests

Perform By: Perform By: Perform By: Perform By: Perform By: Perform By:

Example Value Stream Analysis

Work

W it

RequestApprove & Prioritize

Size & Prioritize

Code Test Deploy

Customersy

Portfolio Manager

Dev Team Dev Team Test Team OpsTeam

Submit Ticket

Assign Team

ScheduleAssign Tester

Wait for Ops

30 min

3 D

30 min

15 D

15 min

15 D

2 Hours

2 Weeks

2 Hours

2 Weeks

8 Hours 15 min

2 Days

2 Hours

2 Days

4 HoursTotal19.5 Hours

9 Weeks

21

Value StreamInception Delivery

Wait 3 Days 15 Days 15 Days 2 Weeks 2 Weeks 2 Days 2 Days 9 Weeks

New Feature Requests

Value Stream Optimized Improvement Opportunities• Eliminate Handoff• Eliminate Work• Automate Work• Combine Multiple Streams of Work

q

Story to Backlog

Size & Prioritize

Code Test Deploy

Perform By:PO

Perform By:Agile Team



Perform By:OpsTeam

Assign Team

ScheduleAssign Tester

Click Button

Total

XX

22

Value StreamInception Delivery

Work

Wait

30 min

15 Days

2 Hours

2 Weeks

2 Hours 8 Hours 20 min 20 min 13 Hours

4 Weeks

11/3/2016

12


Codified Infrastructure + Proactive

Downtime

Reactive Fire Fighting

Angry

23

+ Proactive Monitoring

Customers

Proactive Monitoring – Monitoring Gas Gauge vs. Running out of Fuel in the Middle of DriveRunning out of Fuel in the Middle of Drive

Codified Infrastructure – Automated configuration and provisioning of infrastructure from versionedand provisioning of infrastructure from versioned managed definition

24

11/3/2016

13

Recommendation



Optimize on:• Service Availability• Downtime

1. Apply Business Intelligence to Monitoring

2. Automate Recovery/ Self Healing Infrastructure

1. Start with Configuration + Infrastructure Monitoring

25

• Downtime• Mean Time To

Recovery

Infrastructure Monitoring2. Ensure Monitoring Data is

Visible Across Value Stream

PlanAct

Continuous Improvement Journey

Activities Correlate with

Success?

What Can I Accomplish?

Quarterly Goal

1 Month Goal

1 Week Goal

DoCheck

26

How Do I Measure

Outcome?

Activities I can Perform to

Achieve Goal?

11/3/2016

14

Be a Different Kind of Hero

Chart a Different Future

28

11/3/2016

15

Questions?