Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Continuous Deployment: Startup Lessons Learned

16,515 views

Published on

Published in: Technology

Continuous Deployment: Startup Lessons Learned

  1. Continuous Deployment Case-study: WiredReach COMMIT DEV MONITOR TEST RELEASE QA DEPLOY Ash Maurya @ashmaurya http://www.ashmaurya.com
  2. How do you maximize progress in a Lean Startup?
  3. By maximizing validated learning about customers.
  4. Requirements Development QA Release
  5. Some learning Requirements Development QA Release
  6. Most learning happens Some learning here Requirements Development QA Release
  7. Most learning happens Some learning here Requirements Development QA Release Very little learning
  8. Product Development gets in the way of learning about customers.
  9. Most learning happens Some learning here Requirements Development QA Release Very little learning
  10. Most learning happens Some learning here Requirements Release
  11. Most learning happens Some learning here Requirements Release
  12. Most learning happens Some learning here Requirements Release
  13. Most learning happens Some learning here Continuous Requirements Release Deployment Shortens cycle time
  14. 1. Before and After 2. How we got started 3. How we build features
  15. 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.
  16. Before After COMMIT DEV MONITOR TEST RELEASE QA DEPLOY 2 week release cycles Multiple releases a day
  17. Before After PRODUCTION PRODUCTION CERTIFICATION SANDBOXES Staging area Standalone sandboxes
  18. Before After COMMIT DEV MONITOR TEST RELEASE QA DEPLOY Releases were all day events Releases are non-events
  19. Before After COMMIT DEV MONITOR TEST RELEASE QA DEPLOY Release size: Release size: hundreds of lines of code < 25 lines of code
  20. Before After COMMIT DEV MONITOR TEST RELEASE QA DEPLOY More emergency releases Less firefighting
  21. Before After COMMIT DEV MONITOR TEST RELEASE QA DEPLOY Coding days versus Coding days AND Customer days Customer days
  22. Continuous Deployment sounds great, but...
  23. Taking the plunge is scary as hell
  24. Requirements Development QA Release
  25. Requirements Development QA Release
  26. $ Requirements Development QA Release
  27. $ Requirements Development QA Release Very little learning
  28. $ Automated Requirements Development QA QA Release Very little learning
  29. $ Automated Requirements Development QA QA Release Production Very little learning Monitoring
  30. 1. Before and After 2. How we got started 3. How we build features
  31. Code in small batch sizes
  32. Deploy manually at first, then automate.
  33. Always test the User Activation flow
  34. Watch the release cycle time COMMIT MONITOR TEST DEPLOY Less than 30 minutes
  35. Be ready to stop the production line
  36. Build a cluster immune system. Incrementally. Build a cluster immune system. Incrementally.
  37. Challenges: Downloadable software
  38. 1. Before and After 2. How we got started 3. How we build features
  39. Don’t be a feature pusher NEW FEATURES 20% CONTINUOUS RELEASE 80% EXISTING FEATURES
  40. Constrain the features pipeline Validated Backlog In-Progress Done Learning Was this feature any good?
  41. Closing the loop with validated learning Qualitative Quantitative Start here Verify with data
  42. When is the right time to start ? There is no better time than the present.
  43. 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

×