Dev "Programming" Ops for DevOps Success Damon Edwards - - PowerPoint PPT Presentation

▶
dev programming ops for devops success damon edwards
SMART_READER_LITE
LIVE PREVIEW

Dev "Programming" Ops for DevOps Success Damon Edwards - - PowerPoint PPT Presentation

Jul 06, 2023 398 likes •1.94k views

Dev "Programming" Ops for DevOps Success Damon Edwards @damonedwards dev2ops.org DevOps Cafe Disclosure: DevOps (to me) Disclosure: DevOps (to me) DevOps is not a specific methodology or prescriptive steps only achievable

slide-1
SLIDE 1
slide-2
SLIDE 2

Dev "Programming" Ops for DevOps Success

slide-3
SLIDE 3

Damon Edwards

@damonedwards dev2ops.org DevOps Cafe

slide-4
SLIDE 4

Disclosure: DevOps (to me)

slide-5
SLIDE 5

Disclosure: DevOps (to me)

DevOps is not

  • a specific methodology or prescriptive steps
  • only achievable by “one true way”
  • a job title or group name
slide-6
SLIDE 6

Disclosure: DevOps (to me)

DevOps is not

  • a specific methodology or prescriptive steps
  • only achievable by “one true way”
  • a job title or group name

DevOps is

  • a way of seeing your problems
  • a way of evaluating solutions
  • a way of communicating these things
  • always evolving
slide-7
SLIDE 7

Damon Edwards

DevOps Consulting Automation Design Open Source Tools

slide-8
SLIDE 8

What every business wants

Time-to-market Quality

slide-9
SLIDE 9

What every business wants

Time-to-market Quality Effectiveness

slide-10
SLIDE 10

What every business wants

Time-to-market Quality Effectiveness

Do more, but don’t spend any more!

( )

slide-11
SLIDE 11

What’s stopping them?

slide-12
SLIDE 12

Photo credit: Doc Searls on Flickr

slide-13
SLIDE 13

Photo credit: Doc Searls on Flickr

Ops

Dev

slide-14
SLIDE 14

Photo credit: Doc Searls on Flickr

Wall of Confusion

Ops

Dev

slide-15
SLIDE 15

Photo credit: Doc Searls on Flickr

Ah-ha!

Ops

Dev

Wa ll

  • f

i

  • n
  • nfus

C

Remove Shorten

slide-16
SLIDE 16

Photo credit: Doc Searls on Flickr

You are here DEV

slide-17
SLIDE 17

“...but how can we start a DevOps transformation from our Dev silo?”

slide-18
SLIDE 18

Dev initiated DevOps Transformation

slide-19
SLIDE 19

Dev initiated DevOps Transformation

  • 1. Take an “Operations First” mindset
slide-20
SLIDE 20 Improved Time to Market & Quality Quicker Feedback from Users Business Idea Running Services

Dev Ops

DevOps and Agile

Ops

Security Auditing Compliance Availability

Understand the pressure on Ops

slide-21
SLIDE 21

What is the product?

slide-22
SLIDE 22

What is the product?

  • Are customers paying for a running service?
slide-23
SLIDE 23

What is the product?

  • Are customers paying for a running service?
  • Then the running service is the product
slide-24
SLIDE 24

What is the product?

  • Are customers paying for a running service?
  • Then the running service is the product
  • Operations is your “factory floor” and “storefront”
slide-25
SLIDE 25

What is the product?

  • Are customers paying for a running service?
  • Then the running service is the product
  • Operations is your “factory floor” and “storefront”
  • Everything else is a “parts supplier”
slide-26
SLIDE 26

What is the product?

  • Are customers paying for a running service?
  • Then the running service is the product
  • Operations is your “factory floor” and “storefront”
  • Everything else is a “parts supplier”
  • (Yes, that includes Developers)
slide-27
SLIDE 27

What is the product?

  • Are customers paying for a running service?
  • Then the running service is the product
  • Operations is your “factory floor” and “storefront”
  • Everything else is a “parts supplier”
  • (Yes, that includes Developers)
  • If the service isn’t running, there is no product or

business

slide-28
SLIDE 28

“-ilities” are product features

slide-29
SLIDE 29

“-ilities” are product features

  • Stability, scalability, availability, security,

etc... are all features

slide-30
SLIDE 30

“-ilities” are product features

  • Stability, scalability, availability, security,

etc... are all features

  • Like all features, you get what you invest
slide-31
SLIDE 31

“-ilities” are product features

  • Stability, scalability, availability, security,

etc... are all features

  • Like all features, you get what you invest

Backlog

Funcational Requirements Operational Requirements

  • Operations Requirements should be

first class citizens in your backlog

slide-32
SLIDE 32

You are developing services (not software)

slide-33
SLIDE 33

You are developing services (not software)

  • Software is a service when it is running and

managed

slide-34
SLIDE 34

You are developing services (not software)

  • Software is a service when it is running and

managed

  • Deployment and configuration is automated
slide-35
SLIDE 35

You are developing services (not software)

  • Software is a service when it is running and

managed

  • Deployment and configuration is automated
  • Standard operating procedures are automated
slide-36
SLIDE 36

You are developing services (not software)

  • Software is a service when it is running and

managed

  • Deployment and configuration is automated
  • Standard operating procedures are automated
  • Tests/Health Checks/Monitoring at service level
slide-37
SLIDE 37

You are developing services (not software)

  • Software is a service when it is running and

managed

  • Deployment and configuration is automated
  • Standard operating procedures are automated
  • Tests/Health Checks/Monitoring at service level
  • You are developing a service... so this is part of

your deliverable

slide-38
SLIDE 38

Redefine “done”

slide-39
SLIDE 39

Redefine “done”

Old “Done”

slide-40
SLIDE 40

Redefine “done”

Old “Done”

  • Work is "done" when it moves

downstream

slide-41
SLIDE 41

Redefine “done”

Old “Done”

  • Work is "done" when it moves

downstream

  • No shared sense of "done"
slide-42
SLIDE 42

Redefine “done”

Old “Done”

  • Work is "done" when it moves

downstream

  • No shared sense of "done"
  • Developers commit code to

repository

slide-43
SLIDE 43

Redefine “done”

Old “Done”

  • Work is "done" when it moves

downstream

  • No shared sense of "done"
  • Developers commit code to

repository

  • Time for a party: code complete!
slide-44
SLIDE 44

Redefine “done”

Old “Done”

  • Work is "done" when it moves

downstream

  • No shared sense of "done"
  • Developers commit code to

repository

  • Time for a party: code complete!
  • The work just begins for

Operations to figure out how to run it in production

slide-45
SLIDE 45

Redefine “done”

Old “Done”

  • Work is "done" when it moves

downstream

  • No shared sense of "done"
  • Developers commit code to

repository

  • Time for a party: code complete!
  • The work just begins for

Operations to figure out how to run it in production

New “Done”

slide-46
SLIDE 46

Redefine “done”

Old “Done”

  • Work is "done" when it moves

downstream

  • No shared sense of "done"
  • Developers commit code to

repository

  • Time for a party: code complete!
  • The work just begins for

Operations to figure out how to run it in production

New “Done”

  • It's running
slide-47
SLIDE 47

Redefine “done”

Old “Done”

  • Work is "done" when it moves

downstream

  • No shared sense of "done"
  • Developers commit code to

repository

  • Time for a party: code complete!
  • The work just begins for

Operations to figure out how to run it in production

New “Done”

  • It's running
  • It's managed
slide-48
SLIDE 48

Redefine “done”

Old “Done”

  • Work is "done" when it moves

downstream

  • No shared sense of "done"
  • Developers commit code to

repository

  • Time for a party: code complete!
  • The work just begins for

Operations to figure out how to run it in production

New “Done”

  • It's running
  • It's managed
  • Customer accessible
slide-49
SLIDE 49

Redefine “done”

Old “Done”

  • Work is "done" when it moves

downstream

  • No shared sense of "done"
  • Developers commit code to

repository

  • Time for a party: code complete!
  • The work just begins for

Operations to figure out how to run it in production

New “Done”

  • It's running
  • It's managed
  • Customer accessible
  • Behaving properly
slide-50
SLIDE 50

Redefine “done”

Old “Done”

  • Work is "done" when it moves

downstream

  • No shared sense of "done"
  • Developers commit code to

repository

  • Time for a party: code complete!
  • The work just begins for

Operations to figure out how to run it in production

New “Done”

  • It's running
  • It's managed
  • Customer accessible
  • Behaving properly

Development of a feature can be “done”. But a service is never “done” until it is turned off!

slide-51
SLIDE 51

If you want freedom, take responsibility

slide-52
SLIDE 52

If you want freedom, take responsibility

Old Way

slide-53
SLIDE 53

If you want freedom, take responsibility

Old Way

  • Developers owned feature

requirements

slide-54
SLIDE 54

If you want freedom, take responsibility

Old Way

  • Developers owned feature

requirements

  • Operations owned

performance and uptime

slide-55
SLIDE 55

If you want freedom, take responsibility

Old Way

  • Developers owned feature

requirements

  • Operations owned

performance and uptime

  • QA owned quality
slide-56
SLIDE 56

If you want freedom, take responsibility

Old Way

  • Developers owned feature

requirements

  • Operations owned

performance and uptime

  • QA owned quality
  • Security owned security
slide-57
SLIDE 57

If you want freedom, take responsibility

Old Way

  • Developers owned feature

requirements

  • Operations owned

performance and uptime

  • QA owned quality
  • Security owned security
  • etc...
slide-58
SLIDE 58

If you want freedom, take responsibility

Old Way

  • Developers owned feature

requirements

  • Operations owned

performance and uptime

  • QA owned quality
  • Security owned security
  • etc...

New Way

slide-59
SLIDE 59

If you want freedom, take responsibility

Old Way

  • Developers owned feature

requirements

  • Operations owned

performance and uptime

  • QA owned quality
  • Security owned security
  • etc...

New Way

  • Developers own their application
slide-60
SLIDE 60

If you want freedom, take responsibility

Old Way

  • Developers owned feature

requirements

  • Operations owned

performance and uptime

  • QA owned quality
  • Security owned security
  • etc...

New Way

  • Developers own their application
  • Operations owns infrastructure

and common tooling

slide-61
SLIDE 61

If you want freedom, take responsibility

Old Way

  • Developers owned feature

requirements

  • Operations owned

performance and uptime

  • QA owned quality
  • Security owned security
  • etc...

New Way

  • Developers own their application
  • Operations owns infrastructure

and common tooling

  • Everybody owns quality,

availability, security for the thing they produce and shared responsibility for things that consume it

slide-62
SLIDE 62

If you want freedom, take responsibility

Old Way

  • Developers owned feature

requirements

  • Operations owned

performance and uptime

  • QA owned quality
  • Security owned security
  • etc...

New Way

  • Developers own their application
  • Operations owns infrastructure

and common tooling

  • Everybody owns quality,

availability, security for the thing they produce and shared responsibility for things that consume it

slide-63
SLIDE 63

Dev initiated DevOps Transformation

  • 1. Take an “operations first” mindset
  • 2. Build organizational alignment
slide-64
SLIDE 64

What is organizational alignment?

slide-65
SLIDE 65

What is organizational alignment?

  • 1000’s of small decisions made daily
  • How do we harness that?
slide-66
SLIDE 66

What is organizational alignment?

  • 1000’s of small decisions made daily
  • How do we harness that?
  • Top down is brittle
  • Conditions, people, tools are always

changing... how do we handle that?

slide-67
SLIDE 67

What is organizational alignment?

  • 1000’s of small decisions made daily
  • How do we harness that?
  • Top down is brittle
  • Conditions, people, tools are always

changing... how do we handle that?

  • Alignment is when you know that different

individuals would independently see a set of conditions and arrive at the same decision that is correct for the company’s goal

slide-68
SLIDE 68

What is organizational alignment?

  • 1000’s of small decisions made daily
  • How do we harness that?
  • Top down is brittle
  • Conditions, people, tools are always

changing... how do we handle that?

  • Alignment is when you know that different

individuals would independently see a set of conditions and arrive at the same decision that is correct for the company’s goal

slide-69
SLIDE 69

What does an aligned organization “see”?

slide-70
SLIDE 70

What does an aligned organization “see”?

expanded from

slide-71
SLIDE 71

What does an aligned organization “see”?

  • 1. See the system

expanded from

slide-72
SLIDE 72

What does an aligned organization “see”?

  • 1. See the system
  • 2. Focus on flow

expanded from

slide-73
SLIDE 73

What does an aligned organization “see”?

  • 1. See the system
  • 2. Focus on flow
  • 3. Recognize feedback loops

expanded from

slide-74
SLIDE 74

What does an aligned organization “see”?

  • 1. See the system
  • 2. Focus on flow
  • 3. Recognize feedback loops
  • 4. Look for continuous improvement opportunities

expanded from

slide-75
SLIDE 75

Sure... but how do you do that?

slide-76
SLIDE 76

Building organizational alignment

slide-77
SLIDE 77

Building organizational alignment

  • 1. Socialize the concepts and vocabulary
slide-78
SLIDE 78

Building organizational alignment

  • 1. Socialize the concepts and vocabulary
  • 2. Visualize the system
slide-79
SLIDE 79

Building organizational alignment

  • 1. Socialize the concepts and vocabulary
  • 2. Visualize the system
  • a. value stream mapping
slide-80
SLIDE 80

Building organizational alignment

  • 1. Socialize the concepts and vocabulary
  • 2. Visualize the system
  • a. value stream mapping
  • b. timeline analysis
slide-81
SLIDE 81

Building organizational alignment

  • 1. Socialize the concepts and vocabulary
  • 2. Visualize the system
  • a. value stream mapping
  • b. timeline analysis
  • c. waste analysis
slide-82
SLIDE 82

Value Stream Mapping

Creative Business Release Engineering Development QA Technical Operations Program Management 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

Core business service delivery process

Current state value stream map Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environment Merge project branch Deploy to Performance Web Assets, flows and wireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Develop web assets Bob McNulty L/T 6 weeks P/T H/C S/R 4 weeks 12 5% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Cut project branch Chris Holmes L/T 15 minutes P/T H/C S/R 5 minutes 1 0% Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Cannata L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Fernando Gomez L/T 30 minutes P/T H/C S/R 30 minutes 1 33% 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 Dx2 EP Mx2 W D PD Dx3 Mx3 TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2
slide-83
SLIDE 83

Value Stream Mapping

Creative Business Release Engineering Development QA Technical Operations Program Management 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

Core business service delivery process

Current state value stream map Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environment Merge project branch Deploy to Performance Web Assets, flows and wireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Develop web assets Bob McNulty L/T 6 weeks P/T H/C S/R 4 weeks 12 5% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Cut project branch Chris Holmes L/T 15 minutes P/T H/C S/R 5 minutes 1 0% Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Cannata L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Fernando Gomez L/T 30 minutes P/T H/C S/R 30 minutes 1 33% 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 Dx2 EP Mx2 W D PD Dx3 Mx3 TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2
slide-84
SLIDE 84

Value Stream Mapping

Customer Shared Drive Test Shared Drive Prod Commits Rollout Schedule README MOP Release Schedule PRD PRD Release Memos Tasks QA Forum Ticket Remedy Ticket Estimates Patch Calendar QA forum MOP README ERR ERR MOP, SOP PRD Design Specs 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 = 28d P/T = 7d H/C = 1 S/R = Stephen / Xi Product Program Planning L/T = 105d P/T = 46d H/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 = 45d P/T = 18d H/C = 23 S/R = Bob Smith Preliminary Development L/T = 45d P/T = 21d H/C = 140 S/R = Bob Smith Full Development L/T = 75d P/T = 43d H/C = 130 S/R = Bob Smith Build L/T = 1d P/T = 0.3d H/C = 2 S/R = 33% John Doe Selective Promotion L/T = 90d P/T = 15d H/C = 5 S/R = Steve Young QA Test L/T = 105d P/T = 11d H/C = 42 S/R = Sam Young Engineering Release L/T = 60d P/T = 1d H/C = 1 S/R = >5% Victoria Doe Release Promotion L/T = 60d P/T = 0.2d H/C = 1 S/R = >5% Victoria Doe Cloud Services Release L/T = 60d P/T = 16d H/C = 3 S/R = 3% Reggie / Carlos Change Control L/T = 42d P/T = H/C = S/R = Peter Lee Deploy Release L/T = 90d P/T = 8d H/C = 8 S/R = 2% Lewis S./Peter Y. Server Provisioning L/T = 24d P/T = 4d H/C = 3 S/R = 50% Jen Garza BRD Server Acceptance L/T = 14d P/T = 1d H/C = 4.5 S/R = 15% Lynn A. etc derived reqs. PRD QA Forum Ticket Service pack review L/T = 56d P/T = 7d H/C = 6 S/R = 100% Suresh Wu M PD(3) PD(3) EP M 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 EP M(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
slide-85
SLIDE 85

Value Stream Mapping

Customer Shared Drive Test Shared Drive Prod Commits Rollout Schedule README MOP Release Schedule PRD PRD Release Memos Tasks QA Forum Ticket Remedy Ticket Estimates Patch Calendar QA forum MOP README ERR ERR MOP, SOP PRD Design Specs 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 = 28d P/T = 7d H/C = 1 S/R = Stephen / Xi Product Program Planning L/T = 105d P/T = 46d H/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 = 45d P/T = 18d H/C = 23 S/R = Bob Smith Preliminary Development L/T = 45d P/T = 21d H/C = 140 S/R = Bob Smith Full Development L/T = 75d P/T = 43d H/C = 130 S/R = Bob Smith Build L/T = 1d P/T = 0.3d H/C = 2 S/R = 33% John Doe Selective Promotion L/T = 90d P/T = 15d H/C = 5 S/R = Steve Young QA Test L/T = 105d P/T = 11d H/C = 42 S/R = Sam Young Engineering Release L/T = 60d P/T = 1d H/C = 1 S/R = >5% Victoria Doe Release Promotion L/T = 60d P/T = 0.2d H/C = 1 S/R = >5% Victoria Doe Cloud Services Release L/T = 60d P/T = 16d H/C = 3 S/R = 3% Reggie / Carlos Change Control L/T = 42d P/T = H/C = S/R = Peter Lee Deploy Release L/T = 90d P/T = 8d H/C = 8 S/R = 2% Lewis S./Peter Y. Server Provisioning L/T = 24d P/T = 4d H/C = 3 S/R = 50% Jen Garza BRD Server Acceptance L/T = 14d P/T = 1d H/C = 4.5 S/R = 15% Lynn A. etc derived reqs. PRD QA Forum Ticket Service pack review L/T = 56d P/T = 7d H/C = 6 S/R = 100% Suresh Wu M PD(3) PD(3) EP M 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 EP M(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
slide-86
SLIDE 86

Timeline Analysis

Creative Business Release Engineering Development QA Technical Operations Program Management 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

Core business service delivery process

Current state value stream map Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environment Merge project branch Deploy to Performance Web Assets, flows and wireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Develop web assets Bob McNulty L/T 6 weeks P/T H/C S/R 4 weeks 12 5% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Cut project branch Chris Holmes L/T 15 minutes P/T H/C S/R 5 minutes 1 0% Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Cannata L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Fernando Gomez L/T 30 minutes P/T H/C S/R 30 minutes 1 33% 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 Dx2 EP Mx2 W D PD Dx3 Mx3 TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2
slide-87
SLIDE 87

Waste Analysis

Creative Business Release Engineering Development QA Technical Operations Program Management 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

Core business service delivery process

Current state value stream map Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environment Merge project branch Deploy to Performance Web Assets, flows and wireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Develop web assets Bob McNulty L/T 6 weeks P/T H/C S/R 4 weeks 12 5% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Cut project branch Chris Holmes L/T 15 minutes P/T H/C S/R 5 minutes 1 0% Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Cannata L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Fernando Gomez L/T 30 minutes P/T H/C S/R 30 minutes 1 33% 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 Dx2 EP Mx2 W D PD Dx3 Mx3 TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2
slide-88
SLIDE 88

Waste Analysis

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

slide-89
SLIDE 89

Core business service delivery process

Current state value stream ma

Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environmen Deploy to Performance eb Assets, flows and ireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Canna L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% D Dx2 W D PD TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2

What should we be looking for?

slide-90
SLIDE 90

Core business service delivery process

Current state value stream ma

Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environmen Deploy to Performance eb Assets, flows and ireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Canna L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% D Dx2 W D PD TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2

What should we be looking for?

  • Long lead times (vs processing time)
slide-91
SLIDE 91

Core business service delivery process

Current state value stream ma

Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environmen Deploy to Performance eb Assets, flows and ireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Canna L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% D Dx2 W D PD TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2

What should we be looking for?

  • Long lead times (vs processing time)
  • Request and approval queues
slide-92
SLIDE 92

Core business service delivery process

Current state value stream ma

Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environmen Deploy to Performance eb Assets, flows and ireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Canna L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% D Dx2 W D PD TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2

What should we be looking for?

  • Long lead times (vs processing time)
  • Request and approval queues
  • Large batch sizes
slide-93
SLIDE 93

Core business service delivery process

Current state value stream ma

Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environmen Deploy to Performance eb Assets, flows and ireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Canna L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% D Dx2 W D PD TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2

What should we be looking for?

  • Long lead times (vs processing time)
  • Request and approval queues
  • Large batch sizes
  • Human to human information transfer
slide-94
SLIDE 94

Core business service delivery process

Current state value stream ma

Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environmen Deploy to Performance eb Assets, flows and ireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Canna L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% D Dx2 W D PD TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2

What should we be looking for?

  • Long lead times (vs processing time)
  • Request and approval queues
  • Large batch sizes
  • Human to human information transfer
  • Scrap / Rework / “Backwash”
slide-95
SLIDE 95

Core business service delivery process

Current state value stream ma

Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environmen Deploy to Performance eb Assets, flows and ireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Canna L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% D Dx2 W D PD TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2

What should we be looking for?

  • Long lead times (vs processing time)
  • Request and approval queues
  • Large batch sizes
  • Human to human information transfer
  • Scrap / Rework / “Backwash”
  • Process or tooling inconsistency
slide-96
SLIDE 96

Core business service delivery process

Current state value stream ma

Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environmen Deploy to Performance eb Assets, flows and ireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Canna L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% D Dx2 W D PD TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2

What should we be looking for?

  • Long lead times (vs processing time)
  • Request and approval queues
  • Large batch sizes
  • Human to human information transfer
  • Scrap / Rework / “Backwash”
  • Process or tooling inconsistency
  • Manual deployment / configuration
slide-97
SLIDE 97

Core business service delivery process

Current state value stream ma

Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environmen Deploy to Performance eb Assets, flows and ireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Canna L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% D Dx2 W D PD TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2

What should we be looking for?

  • Long lead times (vs processing time)
  • Request and approval queues
  • Large batch sizes
  • Human to human information transfer
  • Scrap / Rework / “Backwash”
  • Process or tooling inconsistency
  • Manual deployment / configuration
  • Reliance on manual testing / verification
slide-98
SLIDE 98

Core business service delivery process

Current state value stream ma

Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environmen Deploy to Performance eb Assets, flows and ireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Canna L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% D Dx2 W D PD TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2

What should we be looking for?

  • Long lead times (vs processing time)
  • Request and approval queues
  • Large batch sizes
  • Human to human information transfer
  • Scrap / Rework / “Backwash”
  • Process or tooling inconsistency
  • Manual deployment / configuration
  • Reliance on manual testing / verification
  • Injecting requirements late in the process
slide-99
SLIDE 99

Core business service delivery process

Current state value stream ma

Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environmen Deploy to Performance eb Assets, flows and ireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Canna L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% D Dx2 W D PD TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2

What should we be looking for?

  • Long lead times (vs processing time)
  • Request and approval queues
  • Large batch sizes
  • Human to human information transfer
  • Scrap / Rework / “Backwash”
  • Process or tooling inconsistency
  • Manual deployment / configuration
  • Reliance on manual testing / verification
  • Injecting requirements late in the process
  • Fixing in place (vs rebuilding)
slide-100
SLIDE 100

Core business service delivery process

Current state value stream ma

Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environmen Deploy to Performance eb Assets, flows and ireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Canna L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% D Dx2 W D PD TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2

What should we be looking for?

  • Long lead times (vs processing time)
  • Request and approval queues
  • Large batch sizes
  • Human to human information transfer
  • Scrap / Rework / “Backwash”
  • Process or tooling inconsistency
  • Manual deployment / configuration
  • Reliance on manual testing / verification
  • Injecting requirements late in the process
  • Fixing in place (vs rebuilding)
  • “Snowflake” servers and environments
slide-101
SLIDE 101

Core business service delivery process

Current state value stream ma

Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environmen Deploy to Performance eb Assets, flows and ireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Canna L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% D Dx2 W D PD TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2

What should we be looking for?

  • Long lead times (vs processing time)
  • Request and approval queues
  • Large batch sizes
  • Human to human information transfer
  • Scrap / Rework / “Backwash”
  • Process or tooling inconsistency
  • Manual deployment / configuration
  • Reliance on manual testing / verification
  • Injecting requirements late in the process
  • Fixing in place (vs rebuilding)
  • “Snowflake” servers and environments
  • Manual dependency management
slide-102
SLIDE 102

Core business service delivery process

Current state value stream ma

Development Environments Release Build and deploy QA Environments Performance Environment Staging Environment Production Environmen Deploy to Performance eb Assets, flows and ireframes Delta features and fixes Set 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 weeks P/T H/C S/R 4 weeks 5 25% Development Build and deploy Joe Harbaugh L/T 2 days P/T H/C S/R 4 hours 1 10% Development Integration testing Joe Harbaugh L/T 1 day P/T H/C S/R 1 day 5 95% Performance testing Deploy to Production Build test plan Raj Lee L/T 5 days P/T H/C S/R 4 days 1 10% Build test cases Raj Lee L/T 2 weeks P/T H/C S/R 8 days 2 20% Fernando Gomez L/T 8 hours P/T H/C S/R 7 hours 1 2% Acceptance testing Raj Lee L/T 5 days P/T H/C S/R 5 hours 2 10% Feature testing Raj Lee L/T 4 weeks P/T H/C S/R 2.5 weeks 4 20% Allen Cannata L/T 1 week P/T H/C S/R 3 days 1 66% RT tickets Deploy to Staging Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% Staging testing Frances Middleton L/T 1 week P/T H/C S/R 3.5 days 4 66% Allen Canna L/T 9 hours P/T H/C S/R 8 hours 6 66% Frances Middleton L/T 6 days P/T H/C S/R 90 minutes 3 66% D Dx2 W D PD TSx5 Dx2 Wx2 PDx4 EP D PDx3 Mx8 D Wx2 PDx2

What should we be looking for?

  • Long lead times (vs processing time)
  • Request and approval queues
  • Large batch sizes
  • Human to human information transfer
  • Scrap / Rework / “Backwash”
  • Process or tooling inconsistency
  • Manual deployment / configuration
  • Reliance on manual testing / verification
  • Injecting requirements late in the process
  • Fixing in place (vs rebuilding)
  • “Snowflake” servers and environments
  • Manual dependency management
  • Ad-hoc or unstructured artifact management
slide-103
SLIDE 103
  • 1. Socialize the concepts and vocabulary
  • 2. Visualize the system
  • a. value stream mapping
  • b. timeline analysis
  • c. waste analysis

Building organizational alignment

slide-104
SLIDE 104
  • 1. Socialize the concepts and vocabulary
  • 2. Visualize the system
  • a. value stream mapping
  • b. timeline analysis
  • c. waste analysis
  • 3. Pick metrics that matter

Building organizational alignment

slide-105
SLIDE 105

Are you getting better as an organization?

slide-106
SLIDE 106

Are you getting better as an organization?

  • Cycle Time
slide-107
SLIDE 107

Are you getting better as an organization?

  • Cycle Time
  • MTTD (Mean Time To Detect)
slide-108
SLIDE 108

Are you getting better as an organization?

  • Cycle Time
  • MTTD (Mean Time To Detect)
  • MTTR (Mean Time to Repair)
slide-109
SLIDE 109

Are you getting better as an organization?

  • Cycle Time
  • MTTD (Mean Time To Detect)
  • MTTR (Mean Time to Repair)
  • Quality at the Source (Scrap)
slide-110
SLIDE 110

Metrics chains tie the individual to the goal

What matters to the business Capability that influences what matters to the business Activity over which an individual can cause/influence outcomes

slide-111
SLIDE 111
  • 1. Socialize the concepts and vocabulary
  • 2. Visualize the system
  • a. value stream mapping
  • b. timeline analysis
  • c. waste analysis
  • 3. Pick metrics that matter

Building organizational alignment

slide-112
SLIDE 112
  • 1. Socialize the concepts and vocabulary
  • 2. Visualize the system
  • a. value stream mapping
  • b. timeline analysis
  • c. waste analysis
  • 3. Pick metrics that matter
  • 4. Identify projects / experiments against

baseline

Building organizational alignment

slide-113
SLIDE 113
  • 1. Socialize the concepts and vocabulary
  • 2. Visualize the system
  • a. value stream mapping
  • b. timeline analysis
  • c. waste analysis
  • 3. Pick metrics that matter
  • 4. Identify projects / experiments against

baseline

  • 5. Repeat steps 2 - 4

(continuous improvement program)

Building organizational alignment

slide-114
SLIDE 114

Start with a burst of energy

= Principles = Analysis = Design

Agenda

Day 1 Day 2 Day 3 Day 4

Lunch Lunch

Kickoff DevOps Goals Key Concepts Case Study Discussion Current State Analysis Current State Analysis Future State / Solution Design Future State / Solution Design Future State / Solution Design Wrap-up

Lunch Lunch

DevOps Workshop

slide-115
SLIDE 115
  • 1. Socialize the concepts and vocabulary
  • 2. Visualize the system
  • a. value stream mapping
  • b. timeline analysis
  • c. waste analysis
  • 3. Pick metrics that matter
  • 4. Identify projects / experiments against

baseline

  • 5. Repeat steps 2 - 4

(continuous improvement program)

Building organizational alignment

slide-116
SLIDE 116
  • 1. Socialize the concepts and vocabulary
  • 2. Visualize the system
  • a. value stream mapping
  • b. timeline analysis
  • c. waste analysis
  • 3. Pick metrics that matter
  • 1. See the system
  • 4. Identify projects / experiments against

baseline

  • 5. Repeat steps 2 - 4

(continuous improvement program)

Building organizational alignment

slide-117
SLIDE 117
  • 1. Socialize the concepts and vocabulary
  • 2. Visualize the system
  • a. value stream mapping
  • b. timeline analysis
  • c. waste analysis
  • 3. Pick metrics that matter
  • 1. See the system
  • 2. Focus on flow
  • 4. Identify projects / experiments against

baseline

  • 5. Repeat steps 2 - 4

(continuous improvement program)

Building organizational alignment

slide-118
SLIDE 118
  • 1. Socialize the concepts and vocabulary
  • 2. Visualize the system
  • a. value stream mapping
  • b. timeline analysis
  • c. waste analysis
  • 3. Pick metrics that matter
  • 1. See the system
  • 2. Focus on flow
  • 4. Identify projects / experiments against

baseline

  • 5. Repeat steps 2 - 4

(continuous improvement program)

  • 3. Recognize feedback loops

Building organizational alignment

slide-119
SLIDE 119
  • 1. Socialize the concepts and vocabulary
  • 2. Visualize the system
  • a. value stream mapping
  • b. timeline analysis
  • c. waste analysis
  • 3. Pick metrics that matter
  • 1. See the system
  • 2. Focus on flow
  • 4. Identify projects / experiments against

baseline

  • 5. Repeat steps 2 - 4

(continuous improvement program)

  • 3. Recognize feedback loops
  • 4. Look for continuous

improvement opportunities

Building organizational alignment

slide-120
SLIDE 120

Dev initiated DevOps Transformation

  • 1. Take an “operations first” mindset
  • 2. Build organizational alignment
  • 3. Establish a new model for working with Ops
slide-121
SLIDE 121

Example

slide-122
SLIDE 122

What does Dev want?

slide-123
SLIDE 123

What does Dev want?

  • What they need to get their job done
slide-124
SLIDE 124

What does Dev want?

  • What they need to get their job done
  • When they need it
slide-125
SLIDE 125

What does Dev want?

  • What they need to get their job done
  • When they need it
  • Fast feedback
slide-126
SLIDE 126

What does Dev want?

  • What they need to get their job done
  • When they need it
  • Fast feedback
  • Dependable and predictable systems to

integrate with

slide-127
SLIDE 127

What does Dev want?

  • What they need to get their job done
  • When they need it
  • Fast feedback
  • Dependable and predictable systems to

integrate with

  • Limit extraneous information or tasks
slide-128
SLIDE 128

What does Dev want?

  • What they need to get their job done
  • When they need it
  • Fast feedback
  • Dependable and predictable systems to

integrate with

  • Limit extraneous information or tasks
  • For everyone to get out of their way
slide-129
SLIDE 129

What does Ops want?

slide-130
SLIDE 130

What does Ops want?

  • Enough time to do their work
  • Deployment / provisioning
  • Stability and performance engineering
  • Hardening and security
  • Paying down technical debt
  • Compliance
slide-131
SLIDE 131

What does Ops want?

  • Enough time to do their work
  • Deployment / provisioning
  • Stability and performance engineering
  • Hardening and security
  • Paying down technical debt
  • Compliance
  • To have their requirements considered earlier

in the lifecycle

slide-132
SLIDE 132

What does Ops want?

  • Enough time to do their work
  • Deployment / provisioning
  • Stability and performance engineering
  • Hardening and security
  • Paying down technical debt
  • Compliance
  • To have their requirements considered earlier

in the lifecycle

  • Confidence that changes are not going to

break the system or create a vulnerability

slide-133
SLIDE 133

Dev and Ops interact through request queues

slide-134
SLIDE 134

Dev and Ops interact through request queues

X X

Ticket System

??

X

Leads to...

  • Bottlenecks
  • Increased lead times
  • Reinforces organizational silos
  • Misinterpretation or omissions
slide-135
SLIDE 135

Replace request queues with self-service interfaces

slide-136
SLIDE 136

Replace request queues with self-service interfaces

  • Fully automate what used to be done by humans
slide-137
SLIDE 137

Replace request queues with self-service interfaces

  • Fully automate what used to be done by humans
  • Put behind self-service interfaces for on-demand

consumption

slide-138
SLIDE 138

Replace request queues with self-service interfaces

  • Fully automate what used to be done by humans
  • Put behind self-service interfaces for on-demand

consumption

  • Benefits to Ops
  • Less time spent “doing”, more time adding value
  • Stop being the blocker
slide-139
SLIDE 139

Replace request queues with self-service interfaces

  • Fully automate what used to be done by humans
  • Put behind self-service interfaces for on-demand

consumption

  • Benefits to Ops
  • Less time spent “doing”, more time adding value
  • Stop being the blocker
  • Benefits to rest of organization
  • Decouple processes and avoid bottlenecks
  • Each team can move at their own pace
  • Cuts down on scrap and communication overhead
  • Enables a pull-based lifecycle
slide-140
SLIDE 140

Service provider mindset is already familiar

Customers

Ops

Web UI API

slide-141
SLIDE 141

Customers

Ops

Web UI API Dev QA PM / Analysts

Web UI / API Web UI / API Web UI / API

Extend concept to internal interfaces as well

slide-142
SLIDE 142

Why Ops will initially say no

  • Low confidence that new changes won’t

break things

  • Governance / Compliance
  • Auditing
  • Access Control
  • Accounting
slide-143
SLIDE 143

...so lets show them what’s possible step-by-step

slide-144
SLIDE 144

Fully automated, specification driven lifecycle

slide-145
SLIDE 145

Example

Shell Powershell Shell Powershell

slide-146
SLIDE 146

Example

Shell Powershell Shell Powershell

Governance / Compliance

slide-147
SLIDE 147

Mitigate quality and security risks

  • Repeatedly “rehearse” all operations

from earliest possible point in lifecycle

  • Everybody should be deploying and

testing with the same toolchain, automation, and tests

  • QA and InfoSec provide standards and

tooling that are used by Dev upfront

slide-148
SLIDE 148

DEV1 DEV2 DEV3 PERF/STAGE PROD

Confidence

Build confidence from the start

slide-149
SLIDE 149

Pull-based model to control promotions

DEV1 DEV2 DEV3 PERF/STAGE PROD

Confidence

query promote publish

1 2 3

slide-150
SLIDE 150

Don’t forget to give it a name

Operations as a Service (OaaS) Ticketless IT

slide-151
SLIDE 151

Don’t forget to give it a name

Operations as a Service (OaaS) Ticketless IT

More web / cloud friendly Bigger impact with traditional enterprise IT

slide-152
SLIDE 152

Dev initiated DevOps Transformation

  • 1. Take an “operations first” mindset
  • 2. Build organizational alignment
  • 3. Establish a new model for working with Ops
slide-153
SLIDE 153

Damon Edwards

@damonedwards dev2ops.org DevOps Cafe http://www.dtosolutions.com http://www.simplifyops.com

slide-154
SLIDE 154