Continuous Deployment

4,400 views
4,327 views

Published on

My Continuous Deployment talk that I gave at Agile Australia 2010. It was really a collection of different stories about how companies have used CD.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
4,400
On SlideShare
0
From Embeds
0
Number of Embeds
2,017
Actions
Shares
0
Downloads
54
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Continuous Deployment

  1. 1. Continuous Deployment Kane Mar President, Scrumology Pty Ltd http://Scrumology.com Kane@Scrumology.com Agile Australia 2010
  2. 2. In the beginning there was Continuous Integration. “Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day ... Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly.” - Martin Fowler 2
  3. 3. Continuous Deployment is Continuous Integration on steroids. 3
  4. 4. Who’s doing it? 4
  5. 5. Why? Feedback and Value 5
  6. 6. Why? Reduction of waste 6
  7. 7. Why? Crush the competition! 7
  8. 8. An interesting quote ... “We need to get serious about breaking down the silos within our organisations, getting customer focused and driving some real change in the industry. The biggest danger Youi represents is that they will change the expectation and our organisations will not be ready for it.” - Isabel Frederick, Medibank Private 8
  9. 9. Some things to consider ... » Some environments are easier than others » Continuous Deployment for desktop applications is difficult ... but still do-able » Continuous Deployment requires extensive automated testing and monitoring 9
  10. 10. Adopting Continuous Deployment 1. Try ... Adopt Continuous Integration 2. Try ... Stop the (Commit) line 3. Try ... Simple deployment 4. Try ... Realtime alerting 5. Test, test and test some more. 10
  11. 11. Adopting Continuous Deployment Avoid ... Allowing broken tests Avoid ... Unrealistic expectations 11
  12. 12. Keep working towards the goal ... 12
  13. 13. Thank you 13
  14. 14. References 1. http://timothyfitz.wordpress.com/2009/02/10/continuous-deployment-at- imvu-doing-the-impossible-fifty-times-a-day/ 2. http://toni.org/2010/05/19/in-praise-of-continuous-deployment-the- wordpress-com-story/ 3. http://www.startuplessonslearned.com/2009/06/why-continuous- deployment.html 4. http://www.startuplessonslearned.com/2009/06/why-continuous- deployment.html 5. http://about.digg.com/blog/continuous-deployment-code-review-and-pre- tested-commits-digg4 6. http://radar.oreilly.com/2009/03/continuous-deployment-5-eas.html 7. http://www.tcs.com/SiteCollectionDocuments/TCS_News/ APAC_TCSinNews_Insurance_Wealth_Management_Round_Table_06_2010 .pdf 14
  15. 15. Credits http://www.flickr.com/photos/nicholas_t/281820290/ http://www.flickr.com/photos/dnorman/3590132503 http://www.flickr.com/photos/orinrobertjohn/4269470927 http://www.flickr.com/photos/robertvega/3944132320 http://www.flickr.com/photos/ponchosqueal/382476374 15

×