Andrew phillips three-pillars_of_continuous_delivery-1
Upcoming SlideShare
Loading in...5
×
 

Andrew phillips three-pillars_of_continuous_delivery-1

on

  • 125 views

Presentation by Andrew at the recent London Jenkins and Continuous Delivery event

Presentation by Andrew at the recent London Jenkins and Continuous Delivery event

Statistics

Views

Total Views
125
Views on SlideShare
125
Embed Views
0

Actions

Likes
0
Downloads
8
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Andrew phillips three-pillars_of_continuous_delivery-1 Andrew phillips three-pillars_of_continuous_delivery-1 Presentation Transcript

  • Three Pillars of Continuous Delivery: Culture, Practices & Tooling Andrew Phillips, XebiaLabs
  • About Me o  VP Products for XebiaLabs o  Lots of enterprise software development on high-performance systems o  Been on both sides of the “Dev…Ops” fence o  Active open source contributor and committer: jclouds, Akka, Gradle and others o  Cloud, PaaS & JVM language fan (mainly Scala, Clojure) o  Regular meetup, conference etc. presenter
  • About Me o  VP Products for XebiaLabs o  Lots of enterprise software development on highperformance systems o  Been on both sides of the “Dev…Ops” fence o  Active open source contributor and committer: jclouds, Akka, Gradle and others o  Cloud, PaaS & JVM language fan (mainly Scala, Clojure) o  Regular meetup, conference etc. presenter
  • About XebiaLabs o  Leading provider of delivery automation software focused on helping companies deliver higher quality software faster. o  Reduce development applications costs o  Accelerate application time to market o  Bridge the gap between Development and Operations Global Customers, Global Success and many more…
  • Agenda o  Lightning Continuous Delivery Recap o  Tooling, Practices, Culture…how do they relate? o  Bootstrapping a CD Culture o  Crossing “Quick Win Chasm” o  Practical Examples o  Getting Started
  • What Is Continuous Delivery? “Continuous delivery is a set of patterns and best practices that can help software teams dramatically improve the pace and quality of their software delivery.”
  • Why Continuous Delivery? o  Competitive pressure o  Hot trend o  Clear business values o  Accelerate time to market o  Increase application quality o  Increase customer responsiveness
  • Why Continuous Delivery?
  • Aside 1: Continuous Delivery & Agile “Continuous Delivery is a set of patterns and best practices that can help software teams dramatically improve the pace and quality of their software delivery.”
  • Aside 1: Continuous Delivery & Agile “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”
  • Aside 1: Continuous Delivery & Agile
  • Aside 1: Continuous Delivery & Agile “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.” Principle #1 from the Agile Manifesto
  • Aside 2: Continuous Delivery & Devops o  Flood of overlapping messaging in this space right now o  Analysts and new vendors piling on to the bandwagon o  Rather difficult to parse it all at present, especially if you’re coming at this now
  • Aside 2: Continuous Delivery & Devops o  Flood of overlapping messaging in this space right now o  Analysts and new vendors piling on to the bandwagon o  Rather difficult to parse it all at present, especially if you’re coming at this now o  Key point: Whatever you call it, make sure you have some defined goals that are intended to provide some measurable business value o  Happy to debate and discuss definitions over lunch!
  • Three Pillars "   Culture: set of values, beliefs and traditions "   Practices: behaviours and actions that derive from these values and beliefs "   Tooling: instruments used to carry out the behaviours and actions
  • Three Pillars Culture is expressed through Practices carried out using Tooling
  • Three Pillars
  • A Bit About Culture o  Once it’s reached a cultural level: extremely resilient to problems o  If the tooling breaks, people will fix it o  Internal motivation to carry out the practices and make them work o  (Risk of groupthink, so tolerance of open minds is important o  Something for a lunchtime discussion)
  • A Bit About Culture o  Problem: culture is hard to impose from the top down o  Look at history! o  And most organizations are not at the point where a culture is in place o  They’re just starting out on their CD journey! o  So...what can we do about this?
  • Bootstrapping a CD Culture o  Let’s look at those three pillars a different way
  • Bootstrapping a CD Culture Culture is expressed through Practices carried out using Tooling
  • Bootstrapping a CD Culture Culture is expressed through Practices carried out using Tooling
  • Bootstrapping a CD Culture Culture whose effects give rise to Practices enables Tooling
  • Bootstrapping a CD Culture o  Key point here: inverting the causal relationships! o  Why start with tooling & practices?
  • Bootstrapping a CD Culture o  Easy to get up and running o  Certainly compared to culture! o  Low risk o  Largely free or low-cost tools o  “Skunkworks-able” o  Quick, demonstrable effects o  Go after the low hanging fruit!
  • “Quick Win Chasm” o  A story… o  ACME Inc. has heard of this amazing tooling that can help automate their software delivery process o  Consultants come in a build a delivery pipeline o  Runs fine for a while o  Not easy to adapt to new projects, as the consultants have moved on o  Then some parts of the pipeline start to fail, and are switched off or bypassed o  …
  • “Quick Win Chasm” o  Lesson: Tooling by itself only goes so far o  Even if it’s very reliable! o  Resilience comes from making this part of your DNA o  This Is Not Easy! o  Especially since the temptation is to see the initial improvements and stop there
  • Crossing Quick Win Chasm o  Five key points o  Get management buy in o  Find someone who’s “been there” o  Create champions o  Make things visible o  Communicate, communicate, communicate
  • Let’s Get Practical o  Tooling o  Code review
  • Let’s Get Practical o  Tooling o  Code review o  Continuous Integration
  • Let’s Get Practical o  Tooling o  Code review o  Continuous Integration o  Deployment
  • Let’s Get Practical o  Tooling o  Code review o  Continuous Integration o  Deployment o  Testing & quality
  • Let’s Get Practical o  Tooling o  Code review o  Continuous Integration o  Deployment o  Testing & quality o  Provisioning
  • Let’s Get Practical o  Tooling o  Code review o  Continuous Integration o  Deployment o  Testing & quality o  Provisioning o  Orchestration
  • Let’s Get Practical o  Tooling o  Code review o  Continuous Integration o  Deployment o  Testing & quality o  Provisioning o  Orchestration o  Monitoring
  • Let’s Get Practical o  Practices o  Keep changes small
  • Let’s Get Practical o  Practices o  Keep changes small o  Quality before functionality
  • Let’s Get Practical o  Practices o  Keep changes small o  Quality before functionality o  Put the test up front
  • Let’s Get Practical o  Practices o  Keep changes small o  Quality before functionality o  Put the test up front o  Everyone involved early
  • Let’s Get Practical o  Practices o  Keep changes small o  Quality before functionality o  Put the test up front o  Everyone involved early o  No more (code) than necessary
  • Let’s Get Practical o  Practices o  Keep changes small o  Quality before functionality o  Put the test up front o  Everyone involved early o  No more (code) than necessary o  Ongoing user dialog
  • Let’s Get Practical o  Practices o  Keep changes small o  Quality before functionality o  Put the test up front o  Everyone involved early o  No more (code) than necessary o  Ongoing user dialog o  Delivery tooling = serious tooling
  • Let’s Get Practical o  Culture o  We can always do better
  • Let’s Get Practical o  Culture o  We can always do better o  Our service, our features, our users
  • Let’s Get Practical o  Culture o  We can always do better o  Our service, our features, our users o  ‘Us’ includes the business
  • Let’s Get Practical o  Culture o  We can always do better o  Our service, our features, our users o  ‘Us’ includes the business o  Tools work for the team
  • Let’s Get Practical o  Culture o  We can always do better o  Our service, our features, our users o  ‘Us’ includes the business o  Tools work for the team o  Nobody goes home if the build delivery system is broken
  • Getting Started o  Get a baseline: Value Stream Analysis o  Open mind: We Can Do Things Differently o  Define incremental goals o  No Ocean Boiling! o  Start with tooling o  Go after low-hanging fruit
  • Getting Started o  Testing and quality o  More investment and backfilling required o  Requires buy-in o  Adapt your architecture to allow for smaller changes o  Greenfield? Lucky you! o  Otherwise, will need to tackle this eventually o  Full-time business focus o  It’s about putting the business at the wheel! o  Often need some persuasion to actually drive…
  • More Info More Information www.xebialabs.com blog.xebialabs.com Get Started www.xebialabs.com/trial Stay Informed ww.linkedin.com/company/xebialabs @xebialabs
  • Get In Touch! o  Andrew Phillips aphillips at xebialabs dot com o  Talk over lunch or at the XebiaLabs table o  Don’t forget to stop by the XebiaLabs & Cachet Software tables for more information (& swag)
  • Get In Touch! o  Andrew Phillips aphillips at xebialabs dot com o  Talk over lunch or at the XebiaLabs table o  Don’t forget to stop by the XebiaLabs & Cachet Software tables for more information (& swag)
  • Thank you!