Embed Size (px)
DESCRIPTION
Deploying Often. About Me. Doing agile since 1999 Start ups / Enterprises Planigle - Consulting and Training Qcue – VP, Engineering. Case Study: Qcue. SAAS Small team ( DevQAOps ) D eploy every weeknight (for 2 years) Automation and monitoring are key Lots of small issues - PowerPoint PPT Presentation
Citation preview
Deploying Often
© 2012
About MeDoing agile since 1999Start ups / EnterprisesPlanigle - Consulting and TrainingQcue – VP, Engineering
© 2012
Case Study: QcueSAASSmall team (DevQAOps)Deploy every weeknight (for 2 years)Automation and monitoring are keyLots of small issuesFew big issues
© 2012
AgendaWhy do it?PrerequisitesGetting Good At It
© 2012
Value Before Continuous DeployA lot of the literature focuses on going “all
the way”You get a lot of value before thatAnd it is much easier!
© 2012
Customer BenefitsCan turn around fixes / small features quicklyAble to give feedback incrementally
© 2012
Engineering BenefitsEasy to narrow down what caused the
problemEasy to fixKnown stability
© 2012
What if I don’t do SaaS?Deploy to an internal server insteadUse data typical of productionQA, Prod Mgmt, etc. can use itEverything else can still apply
© 2012
DownsidesEvery deploy can crash and burnHave to be vigilantIf done poorly, can spend all your time
recovering
© 2012
Prerequisites – TestingUnit testsIntegration testsAbility to see what it will look like in
production
© 2012
Prerequisites – DeploymentAutomated buildNotification on failurePromote last build that passes
© 2012
Prerequisites – MonitoringWeb site / User monitoringApplication / Guts monitoringLog monitoring
© 2012
Prerequisites – ProcessesWhat if deployment fails?What if your server crashes?What if data is corrupted?What if a critical error gets deployed?
© 2012
Getting Good At It / Tips and TricksDefects are the first priorityIdentify / fix the root causeIdentify / repair holes in testing / monitoringSmall stories helpCode reviews / pair programmingRetrospect often and changeDon’t be disruptiveCommunicate early and often!
© 2012
What if it is TOO BIG?Break into incrementsMake it admin onlyA few customers at a time
© 2012
What if it is too risky?Identify risky areasVary process by riskinessAnyone can block the deploy
© 2012
Messaging to CustomersRelease and Marketing can be distinctFine grained vs. large grained
communication
© 2012
ResourcesWalter Bodwell
Twitter: @wbodwellwww.planigle.com
www.walterbodwell.com
