support and initiate a devops transformation

Leading the Horses to DrinkA Practical Guide to Initiating and Supporting a

DevOps Transformation

DEVOPSDAYS

Damon Edwards

Damon Edwards

@damonedwards

dev2ops.org

DevOps Cafe

damon@simplifyops.com

Wait... SimplifyOps?

rundeck.org

DTO Solutions

DevOpsand

AutomationConsulting

Ah-ha!

OpsDev

Wall of iononfusC

Remove

Shorten

“My managers don’t get it”“Dev group won’t talk to me”“Ops group won’t talk to me”“QA says I’m dangerous”

“My boss told me to buy DevOps by next quarter or else”

“People say they are too busy getting real work done”

“I don’t know where to start”

“How do I explain it”

“I still don’t know where to start”“I still don’t know where to start”“Is anybody listening to me?”“THEY all just don’t get it”

BUT....

3 step process...

3 step processs...

3 step process...

1. Build the “Why?”

Rule #1

“DevOps”

Rule #1

“DevOps”

Rule #1

How we feel

How we feel

How we feel

How we feel

How we feel

How we look to everyone else

How we look to everyone else

How we look to everyone else

How we look to everyone else

DevOps misappropriation

DevOps misappropriation

DevOps misappropriation

Rule #2

There is no other “Why?” than the “Why?” of the business

Rule #2

There is no other “Why?” than the “Why?” of the business

Rule #2

Go ask people

3 step process...

1. Build the “Why?”

2. Build organizational alignment

Ultimate goal: Develop a Common DevOps Vision

Ultimate goal: Develop a Common DevOps Vision

expanded from

Ultimate goal: Develop a Common DevOps Vision

1. See the systemexpanded from

Ultimate goal: Develop a Common DevOps Vision

1. See the system

2. Focus on flow

expanded from

Ultimate goal: Develop a Common DevOps Vision

1. See the system

2. Focus on flow

3. Recognize feedback loops

expanded from

Ultimate goal: Develop a Common DevOps Vision

1. See the system

2. Focus on flow

3. Recognize feedback loops

4. Look for continuous improvement opportunities

expanded from

“DevOps Vision??”

“DevOps Vision??”

Overt actions

Overt actions

1. Teach concepts

Overt actions

1. Teach concepts2. Getting everyone on the same page

Overt actions

1. Teach concepts2. Getting everyone on the same page a. value stream mapping

Overt actions

1. Teach concepts2. Getting everyone on the same page a. value stream mapping b. timeline analysis

Overt actions

1. Teach concepts2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis

Value Stream Mapping

Creative

Business

Release Engineering

Development

QA

Technical Operations

Program Management

L/T Lead timeP/T Process timeH/C Head countS/R Scrap rate

D DefectsEP Extra processesM Motion

PD Partially doneTS Task switchingW Waiting

Core business service delivery process Current state value stream map

DevelopmentEnvironments

ReleaseBuild and deploy

QAEnvironments

PerformanceEnvironment

StagingEnvironment

ProductionEnvironment

Merge project branch

Deploy to Performance

Web Assets, flows and

wireframes

Delta features and

fixesSet of service

branches

Documented test plans and cases

Request QA build

Daily Scrum meeting

Daily Scrum meeting

Deployment Meeting Business Systems

Support

Stan Walters

Change Control

Project Manager

Erica Switzer

Change request

Business Analyst

Erica Switzer

Steering Committee

Erica Switzer

Full Projects / Expedites

Estimates and

requirements

Technical Specification

Deployment Document

Change Control Forms

RT tickets

Jira issues

Jira issues

Tested packages

Development

Joe Harbaugh

L/T 8 weeksP/TH/CS/R

4 weeks525%

Developweb assets

Bob McNulty

L/T 6 weeksP/TH/CS/R

4 weeks125%

DevelopmentBuild and deploy

Joe Harbaugh

L/T 2 daysP/TH/CS/R

4 hours110%

Development Integration testing

Joe Harbaugh

L/T 1 dayP/TH/CS/R

1 day595%

Performance testing

Deploy toProduction

Build test plan

Raj Lee

L/T 5 daysP/TH/CS/R

4 days110%

Build test cases

Raj Lee

L/T 2 weeksP/TH/CS/R

8 days220%

Fernando Gomez

L/T 8 hoursP/TH/CS/R

7 hours12%

Acceptance testing

Raj Lee

L/T 5 daysP/TH/CS/R

5 hours210%

Feature testing

Raj Lee

L/T 4 weeksP/TH/CS/R

2.5 weeks420%

Allen Cannata

L/T 1 weekP/TH/CS/R

3 days166%

RT tickets

Cut project branch

Chris Holmes

L/T 15 minutesP/TH/CS/R

5 minutes10%

Deploy to Staging

Frances Middleton

L/T 6 daysP/TH/CS/R

90 minutes366%

Staging testing

Frances Middleton

L/T 1 weekP/TH/CS/R

3.5 days466%

Allen Cannata

L/T 9 hoursP/TH/CS/R

8 hours666%

Frances Middleton

L/T 6 daysP/TH/CS/R

90 minutes366%

Fernando Gomez

L/T 30 minutesP/TH/CS/R

30 minutes133%

4 weeks

2 weeks

4 weeks

4 weeks

4 hours

1.5 days

1 day 7 hours 5 hours

1 hours 4.5 days

2.5 weeks

1.5 weeks

90 minutes

5.75 days

3.5 days

1.5 days

8 hours

1 hour

Process Time = 62 days

Lead Time = 113 days

D

EP

Dx2EP

Mx2W

DPD

Dx3Mx3

TSx5 Dx2 Wx2 PDx4

EP

DPDx3 Mx8

DWx2

PDx2

Value Stream Mapping

Creative

Business

Release Engineering

Development

QA

Technical Operations

Program Management

L/T Lead timeP/T Process timeH/C Head countS/R Scrap rate

D DefectsEP Extra processesM Motion

PD Partially doneTS Task switchingW Waiting

Core business service delivery process Current state value stream map

DevelopmentEnvironments

ReleaseBuild and deploy

QAEnvironments

PerformanceEnvironment

StagingEnvironment

ProductionEnvironment

Merge project branch

Deploy to Performance

Web Assets, flows and

wireframes

Delta features and

fixesSet of service

branches

Documented test plans and cases

Request QA build

Daily Scrum meeting

Daily Scrum meeting

Deployment Meeting Business Systems

Support

Stan Walters

Change Control

Project Manager

Erica Switzer

Change request

Business Analyst

Erica Switzer

Steering Committee

Erica Switzer

Full Projects / Expedites

Estimates and

requirements

Technical Specification

Deployment Document

Change Control Forms

RT tickets

Jira issues

Jira issues

Tested packages

Development

Joe Harbaugh

L/T 8 weeksP/TH/CS/R

4 weeks525%

Developweb assets

Bob McNulty

L/T 6 weeksP/TH/CS/R

4 weeks125%

DevelopmentBuild and deploy

Joe Harbaugh

L/T 2 daysP/TH/CS/R

4 hours110%

Development Integration testing

Joe Harbaugh

L/T 1 dayP/TH/CS/R

1 day595%

Performance testing

Deploy toProduction

Build test plan

Raj Lee

L/T 5 daysP/TH/CS/R

4 days110%

Build test cases

Raj Lee

L/T 2 weeksP/TH/CS/R

8 days220%

Fernando Gomez

L/T 8 hoursP/TH/CS/R

7 hours12%

Acceptance testing

Raj Lee

L/T 5 daysP/TH/CS/R

5 hours210%

Feature testing

Raj Lee

L/T 4 weeksP/TH/CS/R

2.5 weeks420%

Allen Cannata

L/T 1 weekP/TH/CS/R

3 days166%

RT tickets

Cut project branch

Chris Holmes

L/T 15 minutesP/TH/CS/R

5 minutes10%

Deploy to Staging

Frances Middleton

L/T 6 daysP/TH/CS/R

90 minutes366%

Staging testing

Frances Middleton

L/T 1 weekP/TH/CS/R

3.5 days466%

Allen Cannata

L/T 9 hoursP/TH/CS/R

8 hours666%

Frances Middleton

L/T 6 daysP/TH/CS/R

90 minutes366%

Fernando Gomez

L/T 30 minutesP/TH/CS/R

30 minutes133%

4 weeks

2 weeks

4 weeks

4 weeks

4 hours

1.5 days

1 day 7 hours 5 hours

1 hours 4.5 days

2.5 weeks

1.5 weeks

90 minutes

5.75 days

3.5 days

1.5 days

8 hours

1 hour

Process Time = 62 days

Lead Time = 113 days

D

EP

Dx2EP

Mx2W

DPD

Dx3Mx3

TSx5 Dx2 Wx2 PDx4

EP

DPDx3 Mx8

DWx2

PDx2

Value Stream Mapping

Customer

Shared Drive Test

Shared Drive Prod

Commits

RolloutSchedule

README

MOP

ReleaseSchedule

PRD

PRD

Release Memos

Tasks

QA Forum Ticket

Remedy Ticket

Estimates

Patch Calendar

QA forum

MOP

README

ERR

ERR

MOP, SOP

PRD

DesignSpecs

crit bugs

email

Lockdown control

checklist

New Targets

Remedy Ticket

Single Image Server

XML

BRD

ERR

BTS

QA Environment

Documentum

Production

Packages

Customer communication

L/T = 28dP/T = 7dH/C = 1S/R =

Stephen / Xi

Product Program Planning

L/T = 105dP/T = 46dH/C = 15

S/R = 100%John Robert

Release Program Management

L/T = P/T =H/C =S/R =

Erica Smith

Engineering Planning Process

L/T = 45dP/T = 18dH/C = 23

S/R = Bob SmithPreliminary

Development

L/T = 45dP/T = 21dH/C = 140

S/R = Bob Smith

FullDevelopment

L/T = 75dP/T = 43dH/C = 130

S/R = Bob Smith

Build

L/T = 1dP/T = 0.3d

H/C = 2S/R = 33%John Doe

Selective Promotion

L/T = 90dP/T = 15dH/C = 5S/R =

Steve Young

QA Test

L/T = 105dP/T = 11dH/C = 42

S/R =Sam Young

Engineering Release

L/T = 60dP/T = 1dH/C = 1

S/R = >5%Victoria Doe

Release Promotion

L/T = 60dP/T = 0.2d

H/C = 1S/R = >5%

Victoria Doe

Cloud Services Release

L/T = 60dP/T = 16dH/C = 3

S/R = 3%Reggie / Carlos

Change Control

L/T = 42dP/T =H/C =S/R =

Peter Lee

Deploy Release

L/T = 90dP/T = 8dH/C = 8

S/R = 2%Lewis S./Peter Y.

Server Provisioning

L/T = 24dP/T = 4dH/C = 3

S/R = 50%Jen Garza

BRD

Server Acceptance

L/T = 14dP/T = 1dH/C = 4.5

S/R = 15%Lynn A. etc

derived reqs.

PRD

QA Forum Ticket

Service pack review

L/T = 56dP/T = 7dH/C = 6

S/R = 100%Suresh Wu

M

PD(3)

PD(3)

EPM

EP(2)

PD

M(3)

W(2)M

TS

M(3)

M(2)

W(2)

M(2)

EP

EP

EP(3)

W

W

EP

W

PD

TS(2)

M

M

M(2)

M W(2) EP

M

D

EPM(3)

D

W

EP

PD D(3)

Current state value stream map

L/T Lead time

P/T Process time

H/C Head count

S/R Scrap rate

D Defects

EP Extra processes

M Motion

PD Partially done

TS Task switching

W Waiting

Product Management

Engineering

Cloud Services

Technical Support

Value Stream Mapping

Customer

Shared Drive Test

Shared Drive Prod

Commits

RolloutSchedule

README

MOP

ReleaseSchedule

PRD

PRD

Release Memos

Tasks

QA Forum Ticket

Remedy Ticket

Estimates

Patch Calendar

QA forum

MOP

README

ERR

ERR

MOP, SOP

PRD

DesignSpecs

crit bugs

email

Lockdown control

checklist

New Targets

Remedy Ticket

Single Image Server

XML

BRD

ERR

BTS

QA Environment

Documentum

Production

Packages

Customer communication

L/T = 28dP/T = 7dH/C = 1S/R =

Stephen / Xi

Product Program Planning

L/T = 105dP/T = 46dH/C = 15

S/R = 100%John Robert

Release Program Management

L/T = P/T =H/C =S/R =

Erica Smith

Engineering Planning Process

L/T = 45dP/T = 18dH/C = 23

S/R = Bob SmithPreliminary

Development

L/T = 45dP/T = 21dH/C = 140

S/R = Bob Smith

FullDevelopment

L/T = 75dP/T = 43dH/C = 130

S/R = Bob Smith

Build

L/T = 1dP/T = 0.3d

H/C = 2S/R = 33%John Doe

Selective Promotion

L/T = 90dP/T = 15dH/C = 5S/R =

Steve Young

QA Test

L/T = 105dP/T = 11dH/C = 42

S/R =Sam Young

Engineering Release

L/T = 60dP/T = 1dH/C = 1

S/R = >5%Victoria Doe

Release Promotion

L/T = 60dP/T = 0.2d

H/C = 1S/R = >5%

Victoria Doe

Cloud Services Release

L/T = 60dP/T = 16dH/C = 3

S/R = 3%Reggie / Carlos

Change Control

L/T = 42dP/T =H/C =S/R =

Peter Lee

Deploy Release

L/T = 90dP/T = 8dH/C = 8

S/R = 2%Lewis S./Peter Y.

Server Provisioning

L/T = 24dP/T = 4dH/C = 3

S/R = 50%Jen Garza

BRD

Server Acceptance

L/T = 14dP/T = 1dH/C = 4.5

S/R = 15%Lynn A. etc

derived reqs.

PRD

QA Forum Ticket

Service pack review

L/T = 56dP/T = 7dH/C = 6

S/R = 100%Suresh Wu

M

PD(3)

PD(3)

EPM

EP(2)

PD

M(3)

W(2)M

TS

M(3)

M(2)

W(2)

M(2)

EP

EP

EP(3)

W

W

EP

W

PD

TS(2)

M

M

M(2)

M W(2) EP

M

D

EPM(3)

D

W

EP

PD D(3)

Current state value stream map

L/T Lead time

P/T Process time

H/C Head count

S/R Scrap rate

D Defects

EP Extra processes

M Motion

PD Partially done

TS Task switching

W Waiting

Product Management

Engineering

Cloud Services

Technical Support

Timeline Analysis

Creative

Business

Release Engineering

Development

QA

Technical Operations

Program Management

L/T Lead timeP/T Process timeH/C Head countS/R Scrap rate

D DefectsEP Extra processesM Motion

PD Partially doneTS Task switchingW Waiting

Core business service delivery process Current state value stream map

DevelopmentEnvironments

ReleaseBuild and deploy

QAEnvironments

PerformanceEnvironment

StagingEnvironment

ProductionEnvironment

Merge project branch

Deploy to Performance

Web Assets, flows and

wireframes

Delta features and

fixesSet of service

branches

Documented test plans and cases

Request QA build

Daily Scrum meeting

Daily Scrum meeting

Deployment Meeting Business Systems

Support

Stan Walters

Change Control

Project Manager

Erica Switzer

Change request

Business Analyst

Erica Switzer

Steering Committee

Erica Switzer

Full Projects / Expedites

Estimates and

requirements

Technical Specification

Deployment Document

Change Control Forms

RT tickets

Jira issues

Jira issues

Tested packages

Development

Joe Harbaugh

L/T 8 weeksP/TH/CS/R

4 weeks525%

Developweb assets

Bob McNulty

L/T 6 weeksP/TH/CS/R

4 weeks125%

DevelopmentBuild and deploy

Joe Harbaugh

L/T 2 daysP/TH/CS/R

4 hours110%

Development Integration testing

Joe Harbaugh

L/T 1 dayP/TH/CS/R

1 day595%

Performance testing

Deploy toProduction

Build test plan

Raj Lee

L/T 5 daysP/TH/CS/R

4 days110%

Build test cases

Raj Lee

L/T 2 weeksP/TH/CS/R

8 days220%

Fernando Gomez

L/T 8 hoursP/TH/CS/R

7 hours12%

Acceptance testing

Raj Lee

L/T 5 daysP/TH/CS/R

5 hours210%

Feature testing

Raj Lee

L/T 4 weeksP/TH/CS/R

2.5 weeks420%

Allen Cannata

L/T 1 weekP/TH/CS/R

3 days166%

RT tickets

Cut project branch

Chris Holmes

L/T 15 minutesP/TH/CS/R

5 minutes10%

Deploy to Staging

Frances Middleton

L/T 6 daysP/TH/CS/R

90 minutes366%

Staging testing

Frances Middleton

L/T 1 weekP/TH/CS/R

3.5 days466%

Allen Cannata

L/T 9 hoursP/TH/CS/R

8 hours666%

Frances Middleton

L/T 6 daysP/TH/CS/R

90 minutes366%

Fernando Gomez

L/T 30 minutesP/TH/CS/R

30 minutes133%

4 weeks

2 weeks

4 weeks

4 weeks

4 hours

1.5 days

1 day 7 hours 5 hours

1 hours 4.5 days

2.5 weeks

1.5 weeks

90 minutes

5.75 days

3.5 days

1.5 days

8 hours

1 hour

Process Time = 62 days

Lead Time = 113 days

D

EP

Dx2EP

Mx2W

DPD

Dx3Mx3

TSx5 Dx2 Wx2 PDx4

EP

DPDx3 Mx8

DWx2

PDx2

Waste Analysis

Creative

Business

Release Engineering

Development

QA

Technical Operations

Program Management

L/T Lead timeP/T Process timeH/C Head countS/R Scrap rate

D DefectsEP Extra processesM Motion

PD Partially doneTS Task switchingW Waiting

Core business service delivery process Current state value stream map

DevelopmentEnvironments

ReleaseBuild and deploy

QAEnvironments

PerformanceEnvironment

StagingEnvironment

ProductionEnvironment

Merge project branch

Deploy to Performance

Web Assets, flows and

wireframes

Delta features and

fixesSet of service

branches

Documented test plans and cases

Request QA build

Daily Scrum meeting

Daily Scrum meeting

Deployment Meeting Business Systems

Support

Stan Walters

Change Control

Project Manager

Erica Switzer

Change request

Business Analyst

Erica Switzer

Steering Committee

Erica Switzer

Full Projects / Expedites

Estimates and

requirements

Technical Specification

Deployment Document

Change Control Forms

RT tickets

Jira issues

Jira issues

Tested packages

Development

Joe Harbaugh

L/T 8 weeksP/TH/CS/R

4 weeks525%

Developweb assets

Bob McNulty

L/T 6 weeksP/TH/CS/R

4 weeks125%

DevelopmentBuild and deploy

Joe Harbaugh

L/T 2 daysP/TH/CS/R

4 hours110%

Development Integration testing

Joe Harbaugh

L/T 1 dayP/TH/CS/R

1 day595%

Performance testing

Deploy toProduction

Build test plan

Raj Lee

L/T 5 daysP/TH/CS/R

4 days110%

Build test cases

Raj Lee

L/T 2 weeksP/TH/CS/R

8 days220%

Fernando Gomez

L/T 8 hoursP/TH/CS/R

7 hours12%

Acceptance testing

Raj Lee

L/T 5 daysP/TH/CS/R

5 hours210%

Feature testing

Raj Lee

L/T 4 weeksP/TH/CS/R

2.5 weeks420%

Allen Cannata

L/T 1 weekP/TH/CS/R

3 days166%

RT tickets

Cut project branch

Chris Holmes

L/T 15 minutesP/TH/CS/R

5 minutes10%

Deploy to Staging

Frances Middleton

L/T 6 daysP/TH/CS/R

90 minutes366%

Staging testing

Frances Middleton

L/T 1 weekP/TH/CS/R

3.5 days466%

Allen Cannata

L/T 9 hoursP/TH/CS/R

8 hours666%

Frances Middleton

L/T 6 daysP/TH/CS/R

90 minutes366%

Fernando Gomez

L/T 30 minutesP/TH/CS/R

30 minutes133%

4 weeks

2 weeks

4 weeks

4 weeks

4 hours

1.5 days

1 day 7 hours 5 hours

1 hours 4.5 days

2.5 weeks

1.5 weeks

90 minutes

5.75 days

3.5 days

1.5 days

8 hours

1 hour

Process Time = 62 days

Lead Time = 113 days

D

EP

Dx2EP

Mx2W

DPD

Dx3Mx3

TSx5 Dx2 Wx2 PDx4

EP

DPDx3 Mx8

DWx2

PDx2

Waste Analysis

(Mary Poppendick’s “Seven Wastes of Software Development”)

How do you develop an org’s DevOps Vision?

1. Teach concepts2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis

How do you develop an org’s DevOps Vision?

1. Teach concepts2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis3. Develop metrics chains

Metrics Chains

What matters to the business

Capability that influences what matters to the business

Activity over which an individual can cause/influence outcomes

How do you develop an org’s DevOps Vision?

1. Teach concepts2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis3. Develop metrics chains

How do you develop an org’s DevOps Vision?

1. Teach concepts2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis3. Develop metrics chains 4. Identify projects / experiments against baseline

How do you develop an org’s DevOps Vision?

1. Teach concepts2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis3. Develop metrics chains 4. Identify projects / experiments against baseline5. Repeat steps 2 - 4 (continuous improvement program)

Doing it without talking about “DevOps Vision”!

1. Teach concepts2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis3. Develop metrics chains 4. Identify projects / experiments against baseline5. Repeat steps 2 - 4 (continuous improvement program)

Doing it without talking about “DevOps Vision”!

1. Teach concepts2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis3. Develop metrics chains

1. See the system

4. Identify projects / experiments against baseline5. Repeat steps 2 - 4 (continuous improvement program)

Doing it without talking about “DevOps Vision”!

1. Teach concepts2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis3. Develop metrics chains

1. See the system

2. Focus on flow

4. Identify projects / experiments against baseline5. Repeat steps 2 - 4 (continuous improvement program)

Doing it without talking about “DevOps Vision”!

1. Teach concepts2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis3. Develop metrics chains

1. See the system

2. Focus on flow

4. Identify projects / experiments against baseline5. Repeat steps 2 - 4 (continuous improvement program)

3. Recognize feedback loops

Doing it without talking about “DevOps Vision”!

1. Teach concepts2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis3. Develop metrics chains

1. See the system

2. Focus on flow

4. Identify projects / experiments against baseline5. Repeat steps 2 - 4 (continuous improvement program)

3. Recognize feedback loops

4. Look for continuous improvement opportunities

Important Tool: Workshops

DevOps WorkshopKickstart Your Organization’s Improvement Program

Bring DTO’s recognized DevOps, Service Delivery, and Automation expertise into you company efficiently and effectively. Over the course of 3 days, attendees will learn the methods and best practices that have been used to develop high performance in organizations across the industry.

While theory and high-level concepts are introduced and explained, the focus of this workshop is on imparting practical “nuts and bolts” knowledge that attendees can use immediately in their day-to-day work. By Day 2, your team will be practices new techniques to analyze and diagnose your own DevOps problems. By Day 3, your team will be identifying potential solutions and building an improvement roadmap.

Day 1 Day 2 Day 3

Lunch Lunch Lunch

Agen

da

= Principles = Analysis = Design

Wrap-up

Morning Sessions:• Welcome and Kickoff• Raising the Bar: Trends and

High Performance• Case Study

• Anti-Patterns

Afternoon Sessions:• Successful Design Patterns

• Organization and Process

• Technical • Learning to See: Analyzing

and Diagnosing Problems

Morning Sessions:• Analyzing Your Current State

Afternoon Sessions:• Problem Identification

Techniques

• Improvement Metrics• Technical Deep Dive

Morning Sessions:• Process Improvement and

Automation Toolchain Design

Principles• Solutions Discussion

Afternoon Sessions:• Solutions Discussion (cont’d)• Project Listing and Roadmap

Building

Faster Time to Market

Faster Feedbackfrom Users

BusinessRequest

RunningServices

Improved Quality

OpsDev

3 step processs...

1. Build the “Why?”

2. Build organizational alignment

3. Continuous improvement loops

Continuous Improvement

Plan

Do

Check

Act

Continuous Improvement

Plan

Do

Check

Act

3 step processs...

1. Build the “Why?”

2. Build organizational alignment

3. Continuous improvement loops

A word about breaking silos...