Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Our Continuous Delivery Journey

Our Continuous Delivery Journey

Doing continuous delivery? Got nothing left to learn? Yeah right! The journey to continuous delivery (CD) is long, winding and always evolving. Come hear my stories, learn what worked and what didn't work for us and get some helpful tips!

Originally presented at DevOpsDays Kansas City in October 2016 https://www.devopsdays.org/events/2016-kansascity/program/suzie-prince/

suziejprince

October 21, 2016
Tweet

More Decks by suziejprince

Other Decks in Programming

Transcript

  1. Define Continuous Delivery (CD) Tell some stories about our journey

    to CD Review learnings and share tips WHAT I WILL COVER
  2. Suzie Prince Head of Product for ThoughtWorks products group Product

    Manager for Snap CI 10 + years experience in software development including agile and CD practices Tweeting @pm_suzie
  3. “Continuous Delivery is the ability to get changes of all

    types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.” - Jez Humble, continuousdelivery.com
  4. “Continuous Delivery is the ability to get changes of all

    types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.” - Jez Humble, continuousdelivery.com
  5. Commit Build and Test Automated Tests Staging Deliver User Acceptance

    Commit Build and Test Automated Tests Installer Tests Staging Deliver User Acceptance
  6. Commit Build and Test Automated Tests Staging Deliver User Acceptance

    Commit Build and Test Automated Tests Installer Tests Staging Deliver User Acceptance
  7. Commit Build and Test Automated Tests Staging Deliver User Acceptance

    Commit Build and Test Automated Tests Installer Tests Staging Deliver User Acceptance
  8. Commit Build and Test Automated Tests Staging Deliver User Acceptance

    Commit Build and Test Automated Tests Installer Tests Staging Deliver User Acceptance
  9. “Continuous Delivery is the ability to get changes of all

    types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.” - Jez Humble, continuousdelivery.com
  10. “Continuous Delivery is the ability to get changes of all

    types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.” - Jez Humble, continuousdelivery.com
  11. “Continuous Delivery is the ability to get changes of all

    types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.” - Jez Humble, continuousdelivery.com
  12. “Continuous Delivery is the ability to get changes of all

    types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.” - Jez Humble, continuousdelivery.com
  13. “Continuous Delivery is the ability to get changes of all

    types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.” - Jez Humble, continuousdelivery.com
  14. “Continuous Delivery is the ability to get changes of all

    types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.” - Jez Humble, continuousdelivery.com
  15. CONTINUOUS DELIVERY IS A JOURNEY… Keep your goals in mind

    Look back and retrospect Focus on what is not good now and improve that Don’t be too critical Don’t fear redesign, don’t fear rework
  16. CONTINUOUS DELIVERY IS A JOURNEY… Keep your goals in mind

    Look back and retrospect Focus on what is not good now and improve that Don’t be too critical Don’t fear redesign, don’t fear rework