micro focus devops drive-in with gary gruver - starting and scaling devops in the enterprise...

1

Starting and Scaling DevOps in the Enterprise with Gary Gruver

January 26th 2017, 9:00 am PST

2

Today’s Drive-In Guest Speaker – Gary Gruver

Drive-In Guest Speaker

Gary GruverDevOps Leader and authorGary Gruver Consulting

Drive-In Host

Mark LevyDevOps Evangelist, Dir. Product Marketing

mLevy@serena.comTwitter: @deparko

garygruver.com gary@garygruver.comTwitter: @GRUVERGary

Starting and Scaling DevOps in the Enterprise

Gary Gruver

FW no longer a bottleneck for the business

Development costs reduced from $100M/yr. to $55M/yr.

140% increase in the number of products under development

Capacity for innovation increased from ~5% to ~40% © Gruver Consulting

© Gruver Consulting

© Gruver Consulting

Gene Kim Quote

This is my personal definition: I would define DevOps by the outcomes. In my mind, DevOps is

those set of cultural norms and technology practices that enable the fast flow of planned work from, among others, development, through tests

into operations while preserving world class reliability, operation and security.

DevOps is not about what you do, but what your outcomes are. So many things that we associate

with DevOps fits underneath this very broad umbrella of beliefs and practices—which of

course, communication and culture are part of them.

“

”© Gruver Consulting

© Gruver Consulting

Business Ideas Developer Production

Monitoring

Environment Testing

© Gruver Consulting

Environment TestingDeveloperBusiness

Ideas Production

Monitoring

© Gruver Consulting

Environment TestingDeveloperBusiness

Ideas Production

Monitoring

© Gruver Consulting

Monitoring Monitoring

Environment TestingDeveloperBusiness

Ideas Production

Monitoring

© Gruver Consulting

Monitoring How Long Frequency Issue Source

Environment TestingDeveloperBusiness

Ideas Production

Planning Capacity

Requirements Inventory

% Reworking

% Expected Results

Deploy Time & Effort

Source & Number of New Issues

New Issues

Cycle Time Batch Size

Repeatability

Branch Time

Approval Times

© Gruver Consulting

Segmenting

Tightly Coupled

Loosely Coupled

Non Business Critical

© Gruver Consulting

Tightly Coupled Architecture

A B C

E F G

H I J

D

K

L M

Service Virtualization

Service Virtualization

© Gruver Consulting

Segment with SVA B C

D

E F G

H I J

K

L M

Subsystem I

Subsystem II

Subsystem III

Service Virtualization

Service Virtualization

© Gruver Consulting

Subsystem I Deployment Pipeline

D

C

B

AA

B

C

D

Phase 2 & 3

A B C D

Subsystem I

Subsystem II

Subsystem III

Stage 3

Stage 4BAT

Stage 6Stage 5Regression Production

Full System Deployment Pipeline

Subsystem I

Subsystem II

Subsystem III

Stage 3

Stage 6Stage 4BAT

Stage 5Regression Production

Full System Deployment Pipeline

© Gruver Consulting

Subsystem I

Subsystem II

Subsystem III

Stage 3

Stage 6Stage 4BAT

Stage 5Regression Production

4 Hours

16 Hours

3 Hours 2 Weeks 18 Hours

1 Week

3 Days

1 Day to deploy

2 Days to test

3 Days

Cycle Time and Batch Size Map

© Gruver Consulting

Source of Issue Slide

Subsystem II

Stage 5Regression

Subsystem III

Stage 3

Stage 6Stage 4BAT Production

Subsystem I

Code Environment Test Deploy

Leadership vs Empowerment

Specialization vs Generalist

Push to production

Green builds & Quality Gates

© Gruver Consulting

22

Thank you!