Building a Compelling Business Case for Continuous Delivery

36
Building a Compelling Business Case for Con2nuous Delivery October 6, 2015 Kurt Bi3ner, Forrester Research Andrew Phillips, XebiaLabs

Transcript of Building a Compelling Business Case for Continuous Delivery

Page 1: Building a Compelling Business Case for Continuous Delivery

Building  a  Compelling  Business  Case  for    Con2nuous  Delivery  October  6,  2015    Kurt  Bi3ner,  Forrester  Research  Andrew  Phillips,  XebiaLabs  

Page 2: Building a Compelling Business Case for Continuous Delivery

2

Housekeeping  

▪ This  webinar  is  being  recorded    

▪ Links  to  the  slides  and  the  recording  will  be  made  available  aGer  the  presentaHon    

▪ You  can  post  quesHons  via  the  GoToWebinar  Control  Panel  

Page 3: Building a Compelling Business Case for Continuous Delivery

3

Agenda  

▪ IntroducHon  

▪ Bridging  the  SoGware  Delivery  Divide  

▪ Building  a  Compelling  Business  Case  For  ConHnuous  Delivery  

▪ Q  &  A  

Page 4: Building a Compelling Business Case for Continuous Delivery

4

Presenters  

Andrew  Phillips  

@XebiaLabs  

▪ Lots  of  enterprise  soGware  development  on  high-­‐performance  systems  

▪ Been  on  both  sides  of  the  “Dev…Ops”  fence  

▪ Regular  presents  at  meetups,  conference  etc.    

Kurt  Bi>ner  

@ksbi3ner  

▪ Kurt  Bi3ner  is  a  Principal  Analyst  serving  ApplicaHon  Development  and  Delivery  professionals.  

▪ His  research  focus  in  on  helping  organizaHons  improve  their  speed  and  quality  of  delivery  while  reducing  cost  and  improving  business  performance.  He  focuses  primarily  on  ConHnuous  Delivery  and  DevOps  pracHces.  

Page 5: Building a Compelling Business Case for Continuous Delivery

5

ConnecHng  the  dots  for    Con2nuous  Delivery    at  enterprise  scale  

VIS IB I L I TY  

AUTOMATION  

CONTROL  

G l o b a l   L e a d e r s   D e l i v e r   S o G w a r e   w i t h   X e b i a L a b s  

Page 6: Building a Compelling Business Case for Continuous Delivery

6

VIS IB I L I TY  

AUTOMATION  

CONTROL  

XebiaLabs  Solu2ons  Release  

Orchestra2on  

Deployment  Automa2on    

Test    Analy2cs  

Orchestrate,    automate  +  view    release  pipelines  

Automate  deployment  of  complex    applicaHon  releases    

Analyze  test  results  across  mulHple    test  tools  

ConnecHng  the  dots  for    ConHnuous  Delivery    at  enterprise  scale  

G l o b a l   L e a d e r s   D e l i v e r   S o G w a r e   w i t h   X e b i a L a b s  

Page 7: Building a Compelling Business Case for Continuous Delivery

7

Faster  2me-­‐to-­‐market  

83%  

Reduc2on  in  cycle  2me  90%  

48%   Produc2vity  improvements  

Organiza(ons  with  high  performing  DevOps  [teams]  were  2.5X  more  likely  to  exceed  profitability,  market  share  and  produc;vity  goals  …  .    

 Gene  Kim,  Author  of  The  Phoenix  Project  

…Con(nuous  Delivery…enables  Agile  to  finally  deliver  on  its  promise  to  business  leaders:  faster  delivery  of  genuine  business  value”…    

Kurt  Bi3ner,  Senior  Analyst,  Forrester  Research  

Companies  are  seizing    the  Con2nuous  Delivery  Opportunity  

Page 8: Building a Compelling Business Case for Continuous Delivery

8

OperaHons  

Development  

Architects  

Release  Managers  

IT  professionals  are  looking  to      

▪  Standardized,  repeatable  &  automated  release  processes  

▪  Reduce  risk  (manual  errors,  compliance  +  IT  governance)  

▪  Visibility  across  the  enHre  soGware  delivery  process  

Thing  

>  Legacy   Web   Mobile   Microservice   IoT  

Cloud  On-­‐Prem  Mainframe  

Apps  

Environments  

Tools  

across…    

Page 9: Building a Compelling Business Case for Continuous Delivery

9

The  SoYware  Delivery  Divide    

Bleeding  edge  startup  /  2ger  team  

§  Large-­‐scale  service  landscape  §  MulHple  teams/  organizaHon-­‐

wide  iniHaHve  §  ExisHng  complex  applicaHons  §  Diverse  skill  levels  §  Technical  &  business  scope  

Enterprise  

➡    Tradi(onal  releases   ➡  Con(nuous  Delivery  

▶  Enterprises  want  to  emulate  startups  +  adopt  new  pa3erns  

▶  But  recognize  that  they  are  a  long  way  away  from  that  today  

§  Small  projects  §  Individual  teams  §  Greenfield  §  Highly  skilled  §  Technical  scope  

Page 10: Building a Compelling Business Case for Continuous Delivery

10

Bridging  the  SoYware  Delivery  Divide    

Bleeding  edge  startup  /  2ger  team  

§  Large-­‐scale  service  landscape  §  MulHple  teams/  organizaHon-­‐

wide  iniHaHve  §  ExisHng  complex  applicaHons  §  Diverse  skill  levels  §  Technical  &  business  scope  

Enterprise  

➡  Con(nuous  Delivery  at  Enterprise  Scale  

▶  Enterprises  want  to  emulate  startups  +  adopt  new  pa3erns  

▶  But  recognize  that  they  are  a  long  way  away  from  that  today  

§  Small  projects  §  Individual  teams  §  Greenfield  §  Highly  skilled  §  Technical  scope  

Strategy:  §  Deliver  enterprise-­‐scale  

funcHonality  §  Provide  visibility  into  the  

release  process  §  Ensure  easy  adopHon/use  §  Complement  exisHng  tools  

Page 11: Building a Compelling Business Case for Continuous Delivery

11

From  Theory  to  Prac2ce  

▪ The  ConHnuous  Delivery  story  and  the  promised  benefits  are  compelling  

▪ Addresses  business-­‐relevant  as  well  as  day-­‐to-­‐day  technical  challenges  ▪ Convincing  the  CFO  requires  more  than  a  compelling  story  and  consensus  from  the  team  that  this  is  “a  good  thing  to  do”  

▪ Challenge:  how  to  present  a  credible  business  case  to  allow  you  to  move  from  small  experiments  to  enterprise-­‐wide  ConHnuous  Delivery  iniHaHves?  

Page 12: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited

Page 13: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited

Building a Compelling Business Case For Continuous Delivery

Kurt Bittner, Principal Analyst

Page 14: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 14

Application Delivery Speed is a Force Multiplier

Costs

Benefits

Application Delivery Speed

Cost Revenue

•  Retooling •  Retraining •  Culture ∆

Page 15: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 15

Estimating Costs and Benefits

Magnitude of Impact

Intangibility

Reduced Labor cost

Improved Goodwill

Reduced Defects Reduced

Operating Cost

Improved Competitiveness

Most business cases focus

here

The biggest benefits are

here

Reduced Scrap & Rework

Reduced Production Incidents

Improved Revenue

Improved Delivery Speed

MTTR

Page 16: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 16

Primary Sources of Application Delivery Cost and Waste

Failed deployments

Idea proposed

Understand Needs & Invent

Solutions

Functional Testing

Deploy Solution

Production Support

Load, Performance, Security, …

Testing

UAT/Exploratory

Testing

Release Decision

Wrong solution Scrap and

rework Too much

manual effort

Develop, Commit & Build

Too much manual effort

Provision Environments

Production Incidents

Too much manual effort

Too many meetings

Time spent waiting

Page 17: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 17

Functional Testing

Load, Performance, Security, …

Testing

UAT/Exploratory

Testing

Develop, Commit & Build

Provision Environments Reduced manual effort

Idea proposed

Understand Needs & Invent

Solutions

Deploy Solution

Release Decision

20-80% of Production Incidents Are Due to Configuration Errors

Production

Provision Environments

Testing Development

Manual environment configuration leads to “drift”. Drift causes failures.

Standardization (“infrastructure as code”) + automation eliminates “drift”.

Page 18: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 18

Idea proposed

Understand Needs & Invent

Solutions

Deploy Solution

Release Decision

Benefits of Standardizing Environment Provisioning

Functional Testing

Production Support

Load, Performance, Security, …

Testing

UAT/Exploratory

Testing

Develop, Commit & Build

Provision Environments

Fewer Production Incidents

Reduced manual effort

Reduced time spent waiting

2

1 3

(benefit based on actual effort reduction)

Page 19: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 19

Functional Testing

Load, Performance, Security, …

Testing

UAT/Exploratory

Testing

Develop, Commit & Build

Provision Environments Reduced manual effort

Idea proposed

Understand Needs & Invent

Solutions

Deploy Solution

Release Decision

Production Incidents Are VERY expensive

Production Support

Fewer Production Incidents

•  Data center downtime cost across industries: ~$5,600/minute •  The avg incident length is 90 minutes; avg cost/incident: ~$505,500.

http://www.eweek.com/c/a/IT-Infrastructure/Unplanned-IT-Downtime-Can-Cost-5K-Per-Minute-Report-549007

LOST REVENUE*= (GR/TH) x I x H

GR = gross yearly revenue TH = total yearly business hours

I = percentage impact H = number of hours of outage

http://www.evolven.com/blog/downtime-outages-and-failures-understanding-their-true-costs.html

*Most organizations with customer-facing applications have more accurate models for revenue/loss prediction

Page 20: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 20

Develop, Commit & Build

Provision Environments

Idea proposed

Understand Needs & Invent

Solutions

Release Decision

Production Support

Functional Testing

Load, Performance, Security, …

Testing

UAT/Exploratory

Testing

Deploy Solution

Reducing Costs Caused By Deployment Failures

Failed deployments result in unplanned work: •  Time and effort spent diagnosing problem &

determining remediation steps •  Rolling back failed deployments •  Remediating related production incidents

(don’t forget to include cost of outage)

Business Case impact: based on historical data, determine:

•  average cost per failure •  failure frequency

Page 21: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 21

Develop, Commit & Build

Provision Environments

Idea proposed

Understand Needs & Invent

Solutions

Deploy Solution

Release Decision

Production Support

Manual Testing Is Also VERY Expensive (and not very effective)

Problems with manual testing: •  Slow •  Too expensive to do for each

build – diseconomies of scale •  Coverage typically not very

high •  Manual errors and

inconsistencies

Functional Testing

Load, Performance, Security, …

Testing

UAT/Exploratory

Testing

Solution: •  Increase the amount of

automated API-based testing by shifting some manual tester resources to “Test Development Engineer”

•  Net cost approximately zero •  Over time, manual testing

costs go down

Business Case impact: •  Increased developer productivity •  Reduced production incidents

Page 22: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 22

Functional Testing

Load, Performance, Security, …

Testing

UAT/Exploratory

Testing

Provision Environments

Idea proposed

Understand Needs & Invent

Solutions

Deploy Solution

Release Decision

Production Support

Develop, Commit & Build

Manual Build Processes: inconsistent and hard to control

Problems with manual builds: •  Slow •  Inconsistent

Solution: •  Centralized self-service CI service

Business Case impact: •  Increased developer productivity •  Reduced headcount on teams (or more

resources to write app code)

Page 23: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 23

Develop, Commit & Build Functional

Testing

Load, Performance, Security, …

Testing

UAT/Exploratory

Testing

Provision Environments

Deploy Solution

Release Decision

Production Support

Idea proposed

Understand Needs & Invent

Solutions

Feature Bloat Is A Large But Hidden Cost

Some sobering stats: •  1/3 of ideas have no impact on desired outcomes •  1/3 of ideas make outcomes worse •  Only 1/3 of ideas improve outcomes1

Two-thirds of what gets built is waste!

Page 24: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 24

Develop, Commit & Build Functional

Testing

Load, Performance, Security, …

Testing

UAT/Exploratory

Testing

Provision Environments

Deploy Solution

Release Decision

Idea proposed

Understand Needs & Invent

Solutions

Better Analytics, Faster Delivery Cycles Improve Insight

Improve results by: •  Tying stories and features to outcomes •  Defining desired results •  Delivering in smaller releases to get

feedback faster •  Measuring the outcome using application

analytic tools and practices •  Using data to prioritize future work

Production Support

feedback

Page 25: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 25

A one-point improvement in CX score can result in dramatic increases in revenue

Page 26: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 26

Page 27: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 27

Managing The Delivery Pipeline To Increase Velocity

3 days 5 days

15 days

3 days

10 days 7 days 4 days 9 days

cycle time= 57 days

1 day

feedback

July 25, 2014 “Define A Software Delivery Strategy For Business Innovation”

Idea proposed

Understand Needs & Invent

Solutions

Functional Testing

Deploy Solution

Customer Value

Load, Performance, Security, …

Testing

UAT/Exploratory

Testing

Release Decision

Develop, Commit & Build

Page 28: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 28

Production Support

Functional Testing

Load, Performance, Security, …

Testing

UAT/Exploratory

Testing

Develop, Commit & Build

Provision Environments Reduced manual effort

Idea proposed

Understand Needs & Invent

Solutions

Deploy Solution

Release Decision

Composite Applications Make Coordination Challenging, Delays Likely

Source: Forrester Research, Inc.111102

Figure 2 An Example Modern Application: Composite And Multichannel

Social mediaand search

Systems of engagement(mobile, web, rich client)

Cloud-basedsystems of record

Traditionalsystems of record

In-store point-of-salesystems

Cloud-based services providedby third parties

Page 29: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 29

Production Support

Functional Testing

Load, Performance, Security, …

Testing

UAT/Exploratory

Testing

Develop, Commit & Build

Provision Environments Reduced manual effort

Idea proposed

Understand Needs & Invent

Solutions

Deploy Solution

Release Decision

Revenue Acceleration – Like Outages, But In Reverse

Increased REVENUE = (GR/TH) x I x H

GR = gross yearly revenue TH = total yearly business hours

I = cycle time reduction as % percentage of total year H = number of hours reduction in cycle time

http://www.evolven.com/blog/downtime-outages-and-failures-understanding-their-true-costs.html

Page 30: Building a Compelling Business Case for Continuous Delivery

© 2015 Forrester Research, Inc. Reproduction Prohibited 30

Production Support

Functional Testing

Load, Performance, Security, …

Testing

UAT/Exploratory

Testing

Develop, Commit & Build

Provision Environments Reduced manual effort

Idea proposed

Understand Needs & Invent

Solutions

Deploy Solution

Release Decision

•  The most compelling business outcomes are hard to measure •  Improved customer satisfaction •  Increased revenue •  Increased market share

•  Reducing Production Incidents is the easiest to measure •  Reduced probability of incidents •  Reduced severity •  Improved MTTR

•  Improving productivity and reducing cycle time is always compelling •  Reduced labor cost •  Improved throughput

•  As application modularity increases, speed and complexity increase •  Automation is essential

Summary

Page 31: Building a Compelling Business Case for Continuous Delivery

Thank you

forrester.com

Kurt Bittner, Principal Analyst [email protected]

@ksbittner

Page 32: Building a Compelling Business Case for Continuous Delivery

32

Key  Takeaways  

Include  intangible  benefits  

▶  Harder  to  measure,  but  can  be  the  biggest  benefit  ▶  Ensure  you  make  these  as  visible  as  possible  

Data,  Data,  Data  

Closing  the  loop  

✔  

✔  

✔  

▶  “Black  box”  automa(on  makes  it  hard  to  demonstrate  value  and  to  iden(fy  weak  points  

▶  Tools  must  support  visibility,  automa;on  &  control  

▶  Two-­‐thirds  of  features  will  s(ll  be  neutral  at  best,  even  with  a  perfect  delivery  process  

▶  Hypothesize  before  coding,  measure  in  produc;on  

✔  

Page 33: Building a Compelling Business Case for Continuous Delivery

33

Helping  enterprises  move  to  the  next  level  

“We  reduced  deployment  failure  rates  by  90%”  

“We  went  from  releasing  4  Hmes  a  year  to  bi-­‐weekly  releases    

“Understanding  what’s  broken  in  our  code  takes  minutes  instead  of  days”   …  and  many  more  

Page 34: Building a Compelling Business Case for Continuous Delivery

34 Copyright  2015.    ConfidenHal  –  DistribuHon  prohibited  without  permission    

Next  Steps  

▪ Download  the  IT  Manager’s  Guide    to  Con2nuous  Delivery:  xebialabs.com/it-­‐manager-­‐guide  

▪ Learn  more  about  XebiaLabs  products:  h3ps://xebialabs.com/products/  

▪ Stay  informed:  

             blog.xebialabs.com  

             @xebialabs  

             youtube/xebialabs  

 

Page 35: Building a Compelling Business Case for Continuous Delivery

Ques2ons?  

Page 36: Building a Compelling Business Case for Continuous Delivery

Thank  you!