Presentation is loading. Please wait.

Presentation is loading. Please wait.

© 2012 About Me Doing agile since 1999 Start ups / Enterprises Planigle - Consulting and Training Qcue – VP, Engineering.

Similar presentations


Presentation on theme: "© 2012 About Me Doing agile since 1999 Start ups / Enterprises Planigle - Consulting and Training Qcue – VP, Engineering."— Presentation transcript:

1

2 © 2012 About Me Doing agile since 1999 Start ups / Enterprises Planigle - Consulting and Training Qcue – VP, Engineering

3 © 2012 Case Study: Qcue SAAS Small team (DevQAOps) Deploy every weeknight (for 2 years) Automation and monitoring are key Lots of small issues Few big issues

4 © 2012 Agenda Why do it? Prerequisites Getting Good At It

5 © 2012 Value Before Continuous Deploy A lot of the literature focuses on going “all the way” You get a lot of value before that And it is much easier!

6 © 2012 Customer Benefits Can turn around fixes / small features quickly Able to give feedback incrementally

7 © 2012 Engineering Benefits Easy to narrow down what caused the problem Easy to fix Known stability

8 © 2012 What if I don’t do SaaS? Deploy to an internal server instead Use data typical of production QA, Prod Mgmt, etc. can use it Everything else can still apply

9 © 2012 Downsides Every deploy can crash and burn Have to be vigilant If done poorly, can spend all your time recovering

10 © 2012 Prerequisites – Testing Unit tests Integration tests Ability to see what it will look like in production

11 © 2012 Prerequisites – Deployment Automated build Notification on failure Promote last build that passes

12 © 2012 Prerequisites – Monitoring Web site / User monitoring Application / Guts monitoring Log monitoring

13 © 2012 Prerequisites – Processes What if deployment fails? What if your server crashes? What if data is corrupted? What if a critical error gets deployed?

14 © 2012 Getting Good At It / Tips and Tricks Defects are the first priority Identify / fix the root cause Identify / repair holes in testing / monitoring Small stories help Code reviews / pair programming Retrospect often and change Don’t be disruptive Communicate early and often!

15 © 2012 What if it is TOO BIG? Break into increments Make it admin only A few customers at a time

16 © 2012 What if it is too risky? Identify risky areas Vary process by riskiness Anyone can block the deploy

17 © 2012 Messaging to Customers Release and Marketing can be distinct Fine grained vs. large grained communication

18 © 2012 Resources Walter Bodwell Planigle wbodwell@planigle.com Twitter: @wbodwell www.planigle.com www.walterbodwell.com


Download ppt "© 2012 About Me Doing agile since 1999 Start ups / Enterprises Planigle - Consulting and Training Qcue – VP, Engineering."

Similar presentations


Ads by Google