SlideShare una empresa de Scribd logo
1 de 43
Descargar para leer sin conexión
Continuous Deployment
                Case-study: WiredReach
                                              COMMIT
          DEV




                                    MONITOR            TEST


RELEASE            QA


                                              DEPLOY




                        Ash Maurya
                          @ashmaurya
                  http://www.ashmaurya.com
How do you maximize
progress in a Lean Startup?
By maximizing validated
learning about customers.
Requirements   Development   QA   Release
Some learning




   Requirements   Development   QA   Release
Most learning happens
Some learning
                                              here



   Requirements   Development   QA            Release
Most learning happens
Some learning
                                                   here



   Requirements   Development       QA             Release




                   Very little learning
Product Development gets in the
way of learning about customers.
Most learning happens
Some learning
                                                   here



   Requirements   Development       QA             Release




                   Very little learning
Most learning happens
Some learning
                           here



   Requirements            Release
Most learning happens
Some learning
                           here



   Requirements            Release
Most learning happens
Some learning
                           here



   Requirements            Release
Most learning happens
Some learning
                                  here


                   Continuous
   Requirements                   Release
                   Deployment




            Shortens cycle time
1. Before and After
2. How we got started
3. How we build features
About WiredReach
 Dead-Simple Sharing Software


          BoxCloud
          The simple way to share files
          with clients and coworkers.




          CloudFire
          Photo and Video Sharing for
          Busy Parents and Photographers.
Before                   After
                                    COMMIT
            DEV




                         MONITOR             TEST


RELEASE            QA


                                    DEPLOY




2 week release cycles   Multiple releases a day
Before                 After


  PRODUCTION            PRODUCTION




  CERTIFICATION          SANDBOXES




Staging area      Standalone sandboxes
Before                      After
                                           COMMIT
                DEV




                                MONITOR             TEST


    RELEASE            QA


                                           DEPLOY




Releases were all day events   Releases are non-events
Before                    After
                                       COMMIT
              DEV




                            MONITOR             TEST


  RELEASE            QA


                                       DEPLOY




     Release size:              Release size:
hundreds of lines of code     < 25 lines of code
Before                  After
                                     COMMIT
              DEV




                          MONITOR             TEST


  RELEASE            QA


                                     DEPLOY




More emergency releases     Less firefighting
Before                  After
                                   COMMIT
            DEV




                        MONITOR             TEST


RELEASE            QA


                                   DEPLOY




Coding days versus       Coding days AND
  Customer days           Customer days
Continuous Deployment
  sounds great, but...
Taking the plunge is scary as hell
Requirements   Development   QA   Release
Requirements   Development   QA   Release
$
Requirements   Development   QA   Release
$
Requirements   Development       QA    Release




                Very little learning
$
                              Automated
Requirements   Development       QA
                                 QA       Release




                Very little learning
$
                              Automated
Requirements   Development       QA
                                 QA        Release




                                          Production
                Very little learning      Monitoring
1. Before and After
2. How we got started
3. How we build features
Code in small batch sizes
Deploy manually at first, then automate.
Always test the User Activation flow
Watch the release cycle time


                           COMMIT




                 MONITOR            TEST




                           DEPLOY




                  Less than 30 minutes
Be ready to stop the production line
Build a cluster
immune system.
Incrementally.




   Build a cluster immune system. Incrementally.
Challenges: Downloadable software
1. Before and After
2. How we got started
3. How we build features
Don’t be a feature pusher




         NEW FEATURES



                        20%
                              CONTINUOUS
                                RELEASE

                        80%

           EXISTING
           FEATURES
Constrain the features pipeline




                                            Validated
     Backlog     In-Progress    Done
                                            Learning



               Was this feature any good?
Closing the loop with validated learning


        Qualitative            Quantitative




          Start here           Verify with data
When is the right time to start ?




              There is no better time than the present.
Thanks!
Ash Maurya
twitter: ashmaurya
blog: http://www.ashmaurya.com


         Getting Lean - the book
         How to iterate your web
         application to product/market fit

         http://www.wiredreach.com/gettinglean.html

Más contenido relacionado

La actualidad más candente

Introduction to DevOps | Edureka
Introduction to DevOps | EdurekaIntroduction to DevOps | Edureka
Introduction to DevOps | EdurekaEdureka!
 
A New View of Your Application Security Program with Snyk and ThreadFix
A New View of Your Application Security Program with Snyk and ThreadFixA New View of Your Application Security Program with Snyk and ThreadFix
A New View of Your Application Security Program with Snyk and ThreadFixDenim Group
 
Agile Scrum software methodology
Agile Scrum software methodologyAgile Scrum software methodology
Agile Scrum software methodologyAbdullah Raza
 
Jira as a Tool for Test Management
Jira as a Tool for Test ManagementJira as a Tool for Test Management
Jira as a Tool for Test ManagementMaija Laksa
 
Practical DevSecOps Course - Part 1
Practical DevSecOps Course - Part 1Practical DevSecOps Course - Part 1
Practical DevSecOps Course - Part 1Mohammed A. Imran
 
Getting Started With Cypress
Getting Started With CypressGetting Started With Cypress
Getting Started With CypressKnoldus Inc.
 
What is Shift Left Testing.pdf
What is Shift Left Testing.pdfWhat is Shift Left Testing.pdf
What is Shift Left Testing.pdfTestbytes
 
The Path Towards Spring Boot Native Applications
The Path Towards Spring Boot Native ApplicationsThe Path Towards Spring Boot Native Applications
The Path Towards Spring Boot Native ApplicationsVMware Tanzu
 
Agile Release Planning
Agile Release PlanningAgile Release Planning
Agile Release PlanningAdnan Aziz
 
Scrum process powerpoint ppt slides.
Scrum process powerpoint ppt slides.Scrum process powerpoint ppt slides.
Scrum process powerpoint ppt slides.SlideTeam.net
 
Security Process in DevSecOps
Security Process in DevSecOpsSecurity Process in DevSecOps
Security Process in DevSecOpsOpsta
 

La actualidad más candente (20)

Introduction to DevOps | Edureka
Introduction to DevOps | EdurekaIntroduction to DevOps | Edureka
Introduction to DevOps | Edureka
 
Sonarqube
SonarqubeSonarqube
Sonarqube
 
Scrumban
ScrumbanScrumban
Scrumban
 
"DevOps > CI+CD "
"DevOps > CI+CD ""DevOps > CI+CD "
"DevOps > CI+CD "
 
A New View of Your Application Security Program with Snyk and ThreadFix
A New View of Your Application Security Program with Snyk and ThreadFixA New View of Your Application Security Program with Snyk and ThreadFix
A New View of Your Application Security Program with Snyk and ThreadFix
 
Agile Scrum software methodology
Agile Scrum software methodologyAgile Scrum software methodology
Agile Scrum software methodology
 
Jira training
Jira trainingJira training
Jira training
 
Jira as a Tool for Test Management
Jira as a Tool for Test ManagementJira as a Tool for Test Management
Jira as a Tool for Test Management
 
Practical DevSecOps Course - Part 1
Practical DevSecOps Course - Part 1Practical DevSecOps Course - Part 1
Practical DevSecOps Course - Part 1
 
Getting Started With Cypress
Getting Started With CypressGetting Started With Cypress
Getting Started With Cypress
 
Agile & Scrum Training
Agile & Scrum TrainingAgile & Scrum Training
Agile & Scrum Training
 
What is Shift Left Testing.pdf
What is Shift Left Testing.pdfWhat is Shift Left Testing.pdf
What is Shift Left Testing.pdf
 
The Path Towards Spring Boot Native Applications
The Path Towards Spring Boot Native ApplicationsThe Path Towards Spring Boot Native Applications
The Path Towards Spring Boot Native Applications
 
CANARY DEPLOYMENT
CANARY DEPLOYMENTCANARY DEPLOYMENT
CANARY DEPLOYMENT
 
Agile Release Planning
Agile Release PlanningAgile Release Planning
Agile Release Planning
 
An Overview of SAFe
An Overview of SAFeAn Overview of SAFe
An Overview of SAFe
 
DevSecOps 101
DevSecOps 101DevSecOps 101
DevSecOps 101
 
Scrum process powerpoint ppt slides.
Scrum process powerpoint ppt slides.Scrum process powerpoint ppt slides.
Scrum process powerpoint ppt slides.
 
Security Process in DevSecOps
Security Process in DevSecOpsSecurity Process in DevSecOps
Security Process in DevSecOps
 
HP ALM
HP ALMHP ALM
HP ALM
 

Destacado

10 Steps to Product/Market Fit
10 Steps to Product/Market Fit10 Steps to Product/Market Fit
10 Steps to Product/Market FitAsh Maurya
 
Building a Lean Startup
Building a Lean StartupBuilding a Lean Startup
Building a Lean StartupAsh Maurya
 
Business plan vs Lean Canvas
Business plan vs Lean CanvasBusiness plan vs Lean Canvas
Business plan vs Lean CanvasAsh Maurya
 
Pirate Metrics 2.0 - AARRR
Pirate Metrics 2.0 - AARRRPirate Metrics 2.0 - AARRR
Pirate Metrics 2.0 - AARRRAsh Maurya
 
10 steps to product/market fit
10 steps to product/market fit10 steps to product/market fit
10 steps to product/market fitAsh Maurya
 
Aesop's garden presentation
Aesop's garden presentationAesop's garden presentation
Aesop's garden presentationAsh Maurya
 
Continuous Deployment - Lean LA
Continuous Deployment - Lean LAContinuous Deployment - Lean LA
Continuous Deployment - Lean LAAsh Maurya
 
Actionable metrics
Actionable metricsActionable metrics
Actionable metricsAsh Maurya
 
Lean Canvas Slideshow
Lean Canvas SlideshowLean Canvas Slideshow
Lean Canvas SlideshowAsh Maurya
 
How We Build Features
How We Build FeaturesHow We Build Features
How We Build FeaturesAsh Maurya
 
Running Lean - Dallas
Running Lean - DallasRunning Lean - Dallas
Running Lean - DallasAsh Maurya
 
What Is A Lean Startup?
What Is A Lean Startup?What Is A Lean Startup?
What Is A Lean Startup?Ash Maurya
 
Transitioning to-lean-at-infochimps
Transitioning to-lean-at-infochimpsTransitioning to-lean-at-infochimps
Transitioning to-lean-at-infochimpsAsh Maurya
 
How to Identify a lean startup
How to Identify a lean startupHow to Identify a lean startup
How to Identify a lean startupAsh Maurya
 
Running Lean Canvas
Running Lean CanvasRunning Lean Canvas
Running Lean CanvasAsh Maurya
 
Running lean - YearOneLabs, Montreal
Running lean - YearOneLabs, MontrealRunning lean - YearOneLabs, Montreal
Running lean - YearOneLabs, MontrealAsh Maurya
 
Software MTTR: The Path from Continuous Integration to Continuous Delivery
Software MTTR: The Path from Continuous Integration to Continuous DeliverySoftware MTTR: The Path from Continuous Integration to Continuous Delivery
Software MTTR: The Path from Continuous Integration to Continuous DeliveryJeff Sussna
 
Automated Deployment in Support of Continuous Integration to Transform SDLC
Automated Deployment in Support of Continuous Integration to Transform SDLCAutomated Deployment in Support of Continuous Integration to Transform SDLC
Automated Deployment in Support of Continuous Integration to Transform SDLCDerek Chang
 

Destacado (20)

Vetting ideas
Vetting ideasVetting ideas
Vetting ideas
 
10 Steps to Product/Market Fit
10 Steps to Product/Market Fit10 Steps to Product/Market Fit
10 Steps to Product/Market Fit
 
Building a Lean Startup
Building a Lean StartupBuilding a Lean Startup
Building a Lean Startup
 
Business plan vs Lean Canvas
Business plan vs Lean CanvasBusiness plan vs Lean Canvas
Business plan vs Lean Canvas
 
Pirate Metrics 2.0 - AARRR
Pirate Metrics 2.0 - AARRRPirate Metrics 2.0 - AARRR
Pirate Metrics 2.0 - AARRR
 
10 steps to product/market fit
10 steps to product/market fit10 steps to product/market fit
10 steps to product/market fit
 
Aesop's garden presentation
Aesop's garden presentationAesop's garden presentation
Aesop's garden presentation
 
Continuous Deployment - Lean LA
Continuous Deployment - Lean LAContinuous Deployment - Lean LA
Continuous Deployment - Lean LA
 
Actionable metrics
Actionable metricsActionable metrics
Actionable metrics
 
Lean Canvas Slideshow
Lean Canvas SlideshowLean Canvas Slideshow
Lean Canvas Slideshow
 
How We Build Features
How We Build FeaturesHow We Build Features
How We Build Features
 
Running Lean - Dallas
Running Lean - DallasRunning Lean - Dallas
Running Lean - Dallas
 
What Is A Lean Startup?
What Is A Lean Startup?What Is A Lean Startup?
What Is A Lean Startup?
 
Transitioning to-lean-at-infochimps
Transitioning to-lean-at-infochimpsTransitioning to-lean-at-infochimps
Transitioning to-lean-at-infochimps
 
How to Identify a lean startup
How to Identify a lean startupHow to Identify a lean startup
How to Identify a lean startup
 
Running Lean Canvas
Running Lean CanvasRunning Lean Canvas
Running Lean Canvas
 
Ash sxsw
Ash sxswAsh sxsw
Ash sxsw
 
Running lean - YearOneLabs, Montreal
Running lean - YearOneLabs, MontrealRunning lean - YearOneLabs, Montreal
Running lean - YearOneLabs, Montreal
 
Software MTTR: The Path from Continuous Integration to Continuous Delivery
Software MTTR: The Path from Continuous Integration to Continuous DeliverySoftware MTTR: The Path from Continuous Integration to Continuous Delivery
Software MTTR: The Path from Continuous Integration to Continuous Delivery
 
Automated Deployment in Support of Continuous Integration to Transform SDLC
Automated Deployment in Support of Continuous Integration to Transform SDLCAutomated Deployment in Support of Continuous Integration to Transform SDLC
Automated Deployment in Support of Continuous Integration to Transform SDLC
 

Similar a Continuous Deployment: Startup Lessons Learned

Beyond Scrum: Scaling Agile with Continuous Delivery and Subversion
Beyond Scrum: Scaling Agile with Continuous Delivery and SubversionBeyond Scrum: Scaling Agile with Continuous Delivery and Subversion
Beyond Scrum: Scaling Agile with Continuous Delivery and SubversionProduct Marketing Services
 
Continuous Integration, Continuous Quality, Continuous Delivery
Continuous Integration, Continuous Quality, Continuous DeliveryContinuous Integration, Continuous Quality, Continuous Delivery
Continuous Integration, Continuous Quality, Continuous DeliveryJohn Ferguson Smart Limited
 
Continuous delivery continuous integration 0.3
Continuous delivery continuous integration 0.3Continuous delivery continuous integration 0.3
Continuous delivery continuous integration 0.3Alex Tregubov
 
Releasing fast code - The DevOps approach
Releasing fast code - The DevOps approachReleasing fast code - The DevOps approach
Releasing fast code - The DevOps approachMichael Kopp
 
Continuous delivery chernivcy
Continuous delivery chernivcyContinuous delivery chernivcy
Continuous delivery chernivcyVolodymyr Yelchev
 
Linuxtag 2012 - continuous delivery - dream to reality
Linuxtag 2012  - continuous delivery - dream to realityLinuxtag 2012  - continuous delivery - dream to reality
Linuxtag 2012 - continuous delivery - dream to realityClément Escoffier
 
Flexing your Agile Muscle - Agile Technical Concepts Explained
Flexing your Agile Muscle - Agile Technical Concepts ExplainedFlexing your Agile Muscle - Agile Technical Concepts Explained
Flexing your Agile Muscle - Agile Technical Concepts ExplainedSandy Mamoli
 
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011Marko Taipale
 
Continuous delivery @åf consult
Continuous delivery @åf consultContinuous delivery @åf consult
Continuous delivery @åf consultTomas Riha
 
Release Management for Large Enterprises
Release Management for Large EnterprisesRelease Management for Large Enterprises
Release Management for Large EnterprisesSalesforce Developers
 
Don't hate, automate. lessons learned from implementing continuous delivery
Don't hate, automate. lessons learned from implementing continuous deliveryDon't hate, automate. lessons learned from implementing continuous delivery
Don't hate, automate. lessons learned from implementing continuous deliverySolano Labs
 
SOASTA Webinar: Process Compression For Mobile App Dev 120612
SOASTA Webinar: Process Compression For Mobile App Dev 120612SOASTA Webinar: Process Compression For Mobile App Dev 120612
SOASTA Webinar: Process Compression For Mobile App Dev 120612SOASTA
 
Testing in an Open Source Middleware Platform Space The WSO2 Way.
Testing in an Open Source Middleware Platform Space  The WSO2 Way.Testing in an Open Source Middleware Platform Space  The WSO2 Way.
Testing in an Open Source Middleware Platform Space The WSO2 Way.WSO2
 
Continuous Testing in the Agile Age
Continuous Testing in the Agile AgeContinuous Testing in the Agile Age
Continuous Testing in the Agile AgeBlazeMeter
 
Agile Australia Conference 2011 - Devops live accounts- continuous delivery_st
Agile Australia Conference 2011 - Devops live accounts- continuous delivery_stAgile Australia Conference 2011 - Devops live accounts- continuous delivery_st
Agile Australia Conference 2011 - Devops live accounts- continuous delivery_stNish Mahanty
 
Faster apps. faster time to market. faster mean time to repair
Faster apps. faster time to market. faster mean time to repairFaster apps. faster time to market. faster mean time to repair
Faster apps. faster time to market. faster mean time to repairCompuware ASEAN
 
BizDevOps – Delivering Business Value Quickly at Scale
BizDevOps – Delivering Business Value Quickly at ScaleBizDevOps – Delivering Business Value Quickly at Scale
BizDevOps – Delivering Business Value Quickly at ScaleQASymphony
 

Similar a Continuous Deployment: Startup Lessons Learned (20)

Beyond Scrum: Scaling Agile with Continuous Delivery and Subversion
Beyond Scrum: Scaling Agile with Continuous Delivery and SubversionBeyond Scrum: Scaling Agile with Continuous Delivery and Subversion
Beyond Scrum: Scaling Agile with Continuous Delivery and Subversion
 
Continuous Integration, Continuous Quality, Continuous Delivery
Continuous Integration, Continuous Quality, Continuous DeliveryContinuous Integration, Continuous Quality, Continuous Delivery
Continuous Integration, Continuous Quality, Continuous Delivery
 
How to Introduce Continuous Delivery
How to Introduce Continuous DeliveryHow to Introduce Continuous Delivery
How to Introduce Continuous Delivery
 
Continuous delivery continuous integration 0.3
Continuous delivery continuous integration 0.3Continuous delivery continuous integration 0.3
Continuous delivery continuous integration 0.3
 
Releasing fast code - The DevOps approach
Releasing fast code - The DevOps approachReleasing fast code - The DevOps approach
Releasing fast code - The DevOps approach
 
Continuous delivery chernivcy
Continuous delivery chernivcyContinuous delivery chernivcy
Continuous delivery chernivcy
 
Linuxtag 2012 - continuous delivery - dream to reality
Linuxtag 2012  - continuous delivery - dream to realityLinuxtag 2012  - continuous delivery - dream to reality
Linuxtag 2012 - continuous delivery - dream to reality
 
Flexing your Agile Muscle - Agile Technical Concepts Explained
Flexing your Agile Muscle - Agile Technical Concepts ExplainedFlexing your Agile Muscle - Agile Technical Concepts Explained
Flexing your Agile Muscle - Agile Technical Concepts Explained
 
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
 
Pycon India 12
Pycon India 12Pycon India 12
Pycon India 12
 
Continuous Delivery
Continuous DeliveryContinuous Delivery
Continuous Delivery
 
Continuous delivery @åf consult
Continuous delivery @åf consultContinuous delivery @åf consult
Continuous delivery @åf consult
 
Release Management for Large Enterprises
Release Management for Large EnterprisesRelease Management for Large Enterprises
Release Management for Large Enterprises
 
Don't hate, automate. lessons learned from implementing continuous delivery
Don't hate, automate. lessons learned from implementing continuous deliveryDon't hate, automate. lessons learned from implementing continuous delivery
Don't hate, automate. lessons learned from implementing continuous delivery
 
SOASTA Webinar: Process Compression For Mobile App Dev 120612
SOASTA Webinar: Process Compression For Mobile App Dev 120612SOASTA Webinar: Process Compression For Mobile App Dev 120612
SOASTA Webinar: Process Compression For Mobile App Dev 120612
 
Testing in an Open Source Middleware Platform Space The WSO2 Way.
Testing in an Open Source Middleware Platform Space  The WSO2 Way.Testing in an Open Source Middleware Platform Space  The WSO2 Way.
Testing in an Open Source Middleware Platform Space The WSO2 Way.
 
Continuous Testing in the Agile Age
Continuous Testing in the Agile AgeContinuous Testing in the Agile Age
Continuous Testing in the Agile Age
 
Agile Australia Conference 2011 - Devops live accounts- continuous delivery_st
Agile Australia Conference 2011 - Devops live accounts- continuous delivery_stAgile Australia Conference 2011 - Devops live accounts- continuous delivery_st
Agile Australia Conference 2011 - Devops live accounts- continuous delivery_st
 
Faster apps. faster time to market. faster mean time to repair
Faster apps. faster time to market. faster mean time to repairFaster apps. faster time to market. faster mean time to repair
Faster apps. faster time to market. faster mean time to repair
 
BizDevOps – Delivering Business Value Quickly at Scale
BizDevOps – Delivering Business Value Quickly at ScaleBizDevOps – Delivering Business Value Quickly at Scale
BizDevOps – Delivering Business Value Quickly at Scale
 

Último

100+ ChatGPT Prompts for SEO Optimization
100+ ChatGPT Prompts for SEO Optimization100+ ChatGPT Prompts for SEO Optimization
100+ ChatGPT Prompts for SEO Optimizationarrow10202532yuvraj
 
Governance in SharePoint Premium:What's in the box?
Governance in SharePoint Premium:What's in the box?Governance in SharePoint Premium:What's in the box?
Governance in SharePoint Premium:What's in the box?Juan Carlos Gonzalez
 
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostKubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostMatt Ray
 
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDEADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDELiveplex
 
VoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBXVoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBXTarek Kalaji
 
Computer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and HazardsComputer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and HazardsSeth Reyes
 
Cybersecurity Workshop #1.pptx
Cybersecurity Workshop #1.pptxCybersecurity Workshop #1.pptx
Cybersecurity Workshop #1.pptxGDSC PJATK
 
Introduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxIntroduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxMatsuo Lab
 
9 Steps For Building Winning Founding Team
9 Steps For Building Winning Founding Team9 Steps For Building Winning Founding Team
9 Steps For Building Winning Founding TeamAdam Moalla
 
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Will Schroeder
 
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAAnypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAshyamraj55
 
OpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureOpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureEric D. Schabell
 
UiPath Clipboard AI: "A TIME Magazine Best Invention of 2023 Unveiled"
UiPath Clipboard AI: "A TIME Magazine Best Invention of 2023 Unveiled"UiPath Clipboard AI: "A TIME Magazine Best Invention of 2023 Unveiled"
UiPath Clipboard AI: "A TIME Magazine Best Invention of 2023 Unveiled"DianaGray10
 
Valere | Digital Solutions & AI Transformation Portfolio | 2024
Valere | Digital Solutions & AI Transformation Portfolio | 2024Valere | Digital Solutions & AI Transformation Portfolio | 2024
Valere | Digital Solutions & AI Transformation Portfolio | 2024Alexander Turgeon
 
IEEE Computer Society’s Strategic Activities and Products including SWEBOK Guide
IEEE Computer Society’s Strategic Activities and Products including SWEBOK GuideIEEE Computer Society’s Strategic Activities and Products including SWEBOK Guide
IEEE Computer Society’s Strategic Activities and Products including SWEBOK GuideHironori Washizaki
 
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesAI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesMd Hossain Ali
 
Nanopower In Semiconductor Industry.pdf
Nanopower  In Semiconductor Industry.pdfNanopower  In Semiconductor Industry.pdf
Nanopower In Semiconductor Industry.pdfPedro Manuel
 
Empowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintEmpowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintMahmoud Rabie
 
UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8DianaGray10
 

Último (20)

100+ ChatGPT Prompts for SEO Optimization
100+ ChatGPT Prompts for SEO Optimization100+ ChatGPT Prompts for SEO Optimization
100+ ChatGPT Prompts for SEO Optimization
 
Governance in SharePoint Premium:What's in the box?
Governance in SharePoint Premium:What's in the box?Governance in SharePoint Premium:What's in the box?
Governance in SharePoint Premium:What's in the box?
 
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostKubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
 
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDEADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
 
VoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBXVoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBX
 
Computer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and HazardsComputer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and Hazards
 
Cybersecurity Workshop #1.pptx
Cybersecurity Workshop #1.pptxCybersecurity Workshop #1.pptx
Cybersecurity Workshop #1.pptx
 
Introduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxIntroduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptx
 
9 Steps For Building Winning Founding Team
9 Steps For Building Winning Founding Team9 Steps For Building Winning Founding Team
9 Steps For Building Winning Founding Team
 
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
 
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAAnypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
 
OpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureOpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability Adventure
 
201610817 - edge part1
201610817 - edge part1201610817 - edge part1
201610817 - edge part1
 
UiPath Clipboard AI: "A TIME Magazine Best Invention of 2023 Unveiled"
UiPath Clipboard AI: "A TIME Magazine Best Invention of 2023 Unveiled"UiPath Clipboard AI: "A TIME Magazine Best Invention of 2023 Unveiled"
UiPath Clipboard AI: "A TIME Magazine Best Invention of 2023 Unveiled"
 
Valere | Digital Solutions & AI Transformation Portfolio | 2024
Valere | Digital Solutions & AI Transformation Portfolio | 2024Valere | Digital Solutions & AI Transformation Portfolio | 2024
Valere | Digital Solutions & AI Transformation Portfolio | 2024
 
IEEE Computer Society’s Strategic Activities and Products including SWEBOK Guide
IEEE Computer Society’s Strategic Activities and Products including SWEBOK GuideIEEE Computer Society’s Strategic Activities and Products including SWEBOK Guide
IEEE Computer Society’s Strategic Activities and Products including SWEBOK Guide
 
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesAI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
 
Nanopower In Semiconductor Industry.pdf
Nanopower  In Semiconductor Industry.pdfNanopower  In Semiconductor Industry.pdf
Nanopower In Semiconductor Industry.pdf
 
Empowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintEmpowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership Blueprint
 
UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8
 

Continuous Deployment: Startup Lessons Learned

Notas del editor

  1. Hi - I am Ash with WiredReach and I&apos;m going to be presenting a case-study on how I transitioned from a traditional development process to continuous deployment. Just to get a sense of who is in the room, How many people here know what Continuous Deployment is? And how many people practice Continuous Deployment today?
  2. If I were to ask you &amp;#x201C;How do you maximize progress in a lean startup?&amp;#x201D;, most of you would probably say:
  3. By maximizing learning about customers. We are in a conference about Lean Startups after all.
  4. So lets take a look at where in the development process we learn about customers. Some of this learning happens during the requirements stage in the form of customer discovery when we&amp;#x2019;re out talking to customers and figuring and out what to build. But most of this learning happens only after we get the product into customers&amp;#x2019; hands in the form of customer validation. There is very little learning during development and QA. Sure we learn about other things, just not about customers.
  5. So lets take a look at where in the development process we learn about customers. Some of this learning happens during the requirements stage in the form of customer discovery when we&amp;#x2019;re out talking to customers and figuring and out what to build. But most of this learning happens only after we get the product into customers&amp;#x2019; hands in the form of customer validation. There is very little learning during development and QA. Sure we learn about other things, just not about customers.
  6. So lets take a look at where in the development process we learn about customers. Some of this learning happens during the requirements stage in the form of customer discovery when we&amp;#x2019;re out talking to customers and figuring and out what to build. But most of this learning happens only after we get the product into customers&amp;#x2019; hands in the form of customer validation. There is very little learning during development and QA. Sure we learn about other things, just not about customers.
  7. Even though building a product is the purpose of a startup, you could say that Product Development actually gets in the way of learning about customers.
  8. While we obviously can&amp;#x2019;t eliminate development and QA, we can shorten the cycle time from requirements to release so we can get to the learning parts faster. That is exactly what Continuous Deployment does. Continuous Deployment shortens the cycle time it takes to build, test, and deploy features. Shorter cycle times mean we get feedback faster and learn faster.
  9. While we obviously can&amp;#x2019;t eliminate development and QA, we can shorten the cycle time from requirements to release so we can get to the learning parts faster. That is exactly what Continuous Deployment does. Continuous Deployment shortens the cycle time it takes to build, test, and deploy features. Shorter cycle times mean we get feedback faster and learn faster.
  10. While we obviously can&amp;#x2019;t eliminate development and QA, we can shorten the cycle time from requirements to release so we can get to the learning parts faster. That is exactly what Continuous Deployment does. Continuous Deployment shortens the cycle time it takes to build, test, and deploy features. Shorter cycle times mean we get feedback faster and learn faster.
  11. While we obviously can&amp;#x2019;t eliminate development and QA, we can shorten the cycle time from requirements to release so we can get to the learning parts faster. That is exactly what Continuous Deployment does. Continuous Deployment shortens the cycle time it takes to build, test, and deploy features. Shorter cycle times mean we get feedback faster and learn faster.
  12. Here&amp;#x2019;s an overview of what I&amp;#x2019;ll be talking about today. I&amp;#x2019;ll describe what my development process looked like before and after continuous deployment. I&amp;#x2019;ll talk about how I got started and how I build features now.
  13. Here&amp;#x2019;s some background on WiredReach and the type of products we build. We&amp;#x2019;ve been in business for 7 years and have launched 2 products - BoxCloud and CloudFire. The first product BoxCloud was built using a release early, release often methodology while CloudFire was built using Lean Startup techniques. Both products are hybrid web/desktop applications. What I mean by that is they have both a web component and a downloaded client component which runs on mac and windows.
  14. So, before Continuous Deployment, we used to release on a 2 week cycle which is fairly fast by most standards. We used to spend about a week in development and then QA tested for another 2-3 days before we deployed to customers. Now we release multiple times a day.
  15. Before Continuous Deployment, we had a common staging area that mirrored production. This is what we used for development and QA. It worked fine in the early days but as we grew, coordinating around a single staging area became a problem. Now we build complete standalone sandboxes for development and QA. Each developer has the complete system on their workstation which gives them a lot more freedom to experiment. Each QA machine also runs on a standalone sandbox which makes it easier for us to do isolated testing as well as scale the testing infrastructure horizontally.
  16. Before Continuous Deployment, releases were all day events. We would do a code freeze typically on a Thursday and spend most of Friday building, testing and packaging a release. Now a release is triggered automatically every time we commit code. The system is run against a battery of tests and only deployed into production if it passes all the tests. We constantly monitor the production environment and can tell good changes from bad changes quickly and revert a release if we need to. Our release process currently takes about 20 minutes.
  17. Before Continuous Deployment, the average size of a release was measured in hundreds of lines of code. Now a typical release is under 25 lines of code.
  18. When you are committing 25 lines of code versus hundreds per release, the impact on the system is much more localized. This has led to fewer production emergencies and less firefighting for us.
  19. But most important of all, if you are a technical founder like me, you constantly have to trade-off outside the building activities like customer development against inside the building activities like product development. Before Continuous Deployment, I had to schedule my week for coding days and customer days. Now I can do both in the same day. I schedule my coding in 2 hour blocks usually early in the day. That leaves the rest of the day open for everything else.
  20. So, Continuous Deployment sounds great in theory.
  21. But taking the plunge was still scary. The biggest reason for us was having the feeling of there being no safety net. With a traditional development process, there is a QA cycle before deployment which provides a safety net of time and there is some comfort in sharing testing responsibility with someone else.
  22. But taking more time in QA was not always optimal for us: - despite our best testing efforts, bugs still crept into production - bugs got more expensive and harder to fix the longer we waited - but most important of all, we felt we weren&amp;#x2019;t learning anything about customers during that time The answer isn&amp;#x2019;t taking more time in QA but less through test automation and getting better at detecting and fixing issues in production.
  23. But taking more time in QA was not always optimal for us: - despite our best testing efforts, bugs still crept into production - bugs got more expensive and harder to fix the longer we waited - but most important of all, we felt we weren&amp;#x2019;t learning anything about customers during that time The answer isn&amp;#x2019;t taking more time in QA but less through test automation and getting better at detecting and fixing issues in production.
  24. But taking more time in QA was not always optimal for us: - despite our best testing efforts, bugs still crept into production - bugs got more expensive and harder to fix the longer we waited - but most important of all, we felt we weren&amp;#x2019;t learning anything about customers during that time The answer isn&amp;#x2019;t taking more time in QA but less through test automation and getting better at detecting and fixing issues in production.
  25. But taking more time in QA was not always optimal for us: - despite our best testing efforts, bugs still crept into production - bugs got more expensive and harder to fix the longer we waited - but most important of all, we felt we weren&amp;#x2019;t learning anything about customers during that time The answer isn&amp;#x2019;t taking more time in QA but less through test automation and getting better at detecting and fixing issues in production.
  26. But taking more time in QA was not always optimal for us: - despite our best testing efforts, bugs still crept into production - bugs got more expensive and harder to fix the longer we waited - but most important of all, we felt we weren&amp;#x2019;t learning anything about customers during that time The answer isn&amp;#x2019;t taking more time in QA but less through test automation and getting better at detecting and fixing issues in production.
  27. So lets take a look at how we got started.
  28. The first and most important practice we adopted was fitting releases into small batch sizes. Coding in small batches is the key concept in continuous deployment and can directly be attributed back to shorter cycle times, faster feedback, and a better work flow. For me, a small batch is the output of a 2 hour work block. We can not always build a full feature in 2 hours but we have gotten good at deploying features incrementally. We start with non-user facing changes first, like api updates and database changes, before building user-facing changes. Even deploying these changes early greatly help to lower the integration risk of a feature.
  29. The next thing we did was not try to achieve 100% automation from the start. We kept deploying these small batch releases manually for a while and audited everything we did. This helped us build confidence in the process and overcome some of the initial fear of loosing control. We already had a continuous integration server that ran a large collection of unit tests but once we took out the formal QA step, we found ourselves preferring functional tests over unit tests since they were much better at reflecting what users actually did with the system.
  30. We now have a practice of writing a new functional test with every user facing change, but we didn&amp;#x2019;t start that way. We got started by writing a single test for the user activation flow first. This is the path users take when they first signup, download and interact with our product. If something goes wrong here, nothing else matters after that.
  31. One downside of relying on more functional tests is that they take much longer to run and can drive up the release cycle time. Our goal was to keep the release cycle time under 30 minutes and we were only able to achieve that by distributing the tests across multiple machines. This is where the standalone sandboxes really come in handy. As we add more tests, it is fairly easy for us to add more test boxes and keep the cycle time in check.
  32. Another problem with tests is that over time, they get out of date and start failing. I&amp;#x2019;ve worked in places where developers start ignoring these which is a slippery slope as the problem only keeps getting worse. In Continuous Deployment, these tests are your only line of defense before deploying code, so you have to take failing tests very seriously. We only deploy a release if it passes all the tests. Otherwise, we stop and fix the tests first.
  33. You&amp;#x2019;ll eventually want to build one of these cluster immune systems (just hopefully not that one) that can automatically tell good changes from bad ones and do something about it. But here too, it&amp;#x2019;s important to build it out incrementally. We got started simply monitoring the health of production servers using off-the-shelf tools like ganglia and nagios. Over time we built other application and business level monitoring into it. We did this mostly reactively to production issues. 5Whys.
  34. One of the challenges we faced was adopting continuous deployment for the downloaded client component. Interrupting customers multiple times a day for updates was not an option so we had to build a software update process that updated itself transparently in the background without any user intervention. We also wanted to be able to both push and pull for updates so that we could control how and when we delivered updates. This took some time and experimentation to get right.
  35. Lastly, I want to spend some time talking about how I build features. Continuous Deployment shortens the cycle time it takes to deploy features but how do you make sure you&amp;#x2019;re actually building what customers want and not simply cranking out new features faster. Here are some rules we follow.
  36. Features must be pulled not pushed. If you&amp;#x2019;ve followed a customer discovery process, identified your top 3 problems, and defined a mvp, you do not need to push more features until you have validated your mvp. This doesn&amp;#x2019;t mean you stop development, but most of your time should be spent measuring and improving existing features versus chasing after new problems to solve. From experience, I know this can be a hard rule to enforce and the next rule helps with that.
  37. A good practice for ensuring the 80/20 rule is constraining the features pipeline. This is a common practice from Agile and Kanban, but with the addition of a validated learning state. Here&amp;#x2019;s how it works: Ideally, a new feature must be pulled or tested with more than one customer for it to show up in the backlog. The number of features in-progress is constrained by the number of developers and so is the number of features waiting for validation. This ensures that you cannot deploy a new feature until a previously deployed feature has been validated.
  38. So how do you validate a feature? Unless you have a lot of traffic, quantitative metrics can take some time to collect. For this reason, I prefer to validate a feature qualitatively first. Once a feature goes live, I directly contact customers that expressed interest in that feature and ask them for feedback. It&amp;#x2019;s important not just to test the coolness factor of a feature but that it actually solves a customer problem and more importantly makes or keeps the sale. If I don&amp;#x2019;t get a strong initial signal, I try and figure out why and either improve or kill the feature. We use google website optimizer, KISSmetrics, Mixpanel, and homegrown scripts to collect quantitative data. It&amp;#x2019;s important here too, to focus on the macro and track key metrics over time, like revenue and retention, versus just clicks.
  39. So when is the best time to adopt Continuous Deployment? I believe the ideal time is as early in the product development cycle as possible - when you are small and have a few or even no customers. Continuous Deployment is an incremental process that you have to practice to get really good at. But even adopting simple practices like &amp;#x201C;coding in small batch sizes&amp;#x201D; paid off for us very quickly. The biggest benefit we have derived from Continuous Deployment is the ability to integrate Customer Development with Product Development. The fundamental call to action from Continuous Deployment is to &amp;#x201C;Ship More Frequently&amp;#x201D;. Once you take that first step, what you need to do next becomes clearer. Thank you.