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.

20171030 (tdc) continuously delivering continuous delivery

813 views

Published on

Continuously delivering continuous delivery talk at Trondheim Developer Conference

Published in: Engineering
  • Be the first to comment

  • Be the first to like this

20171030 (tdc) continuously delivering continuous delivery

  1. 1. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 1 @kimvanwilgen | www.kimvanwilgen.com Continuously delivering continuous delivery Kim van Wilgen www.kimvanwilgen.com
  2. 2. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 2 Kim van Wilgen Head of Software development at ANVA Former head of IT at Klaverblad Business background Managing since 2005 @kimvanwilgen nl.linkedin.com/kimvanwilgen kimvanwilgen@gmail.com www.kimvanwilgen.com
  3. 3. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 4 Continuous Delivery (CD) is a set of practices and principles in software engineering aimed at, building, testing, and releasing software, faster and more frequently. These principles help reduce the cost, time and risk of delivering changes, and ultimately value, to customers by allowing for more incremental changes to applications in production. Wikipedia, 2017
  4. 4. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 5 Build up value and reduce risk The value of incremental change
  5. 5. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 6 Small projects vs. Large projects From: the Chaos manifesto 2013, The Standish group
  6. 6. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 7 Feedback and data grow value and innovation The value of incremental change
  7. 7. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 8 Building the right thing Having 14% vs 64% unused features
  8. 8. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 11 What is continuous Klaverblad ANVA ANVA Klaverblad Amazon
  9. 9. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 12 Tool focused No requirements or product vision Distributed over teams Besides other projects So let’s go
  10. 10. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 13 @kimvanwilgen | www.kimvanwilgen.com Results Incomplete tests No shipping choice No monitoring No compliance or control
  11. 11. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 14 Continuous delivery means you’re building software. So treat is as a software development process Lesson #1
  12. 12. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 15 Backlog and prioritizing items
  13. 13. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 16
  14. 14. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 17 Level 1 Dev Staging Test Integration Acceptance Production Dev Staging Test For each component Full landscapeDev Staging Test Manual Dev Staging Test Manual Integration Scenario / UI testing Acceptance Production Add tests and metrics Add monitoring Add reviews
  15. 15. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 18 Improve and maturize Testing Security Performance Mutation Experimenting A/B testing Canary releasing Blue / green deployments Data driven decisions Releasing Walkthroughs Chatbots Distributed releasing Health Issue tracking Build status Monitoring Immutable servers
  16. 16. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 19 Build pipeline Insight in process, status and workflow management
  17. 17. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 23 Monitoring Instant response and proactive support
  18. 18. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 24 Static analysis Knowing quality @kimvanwilgen24
  19. 19. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 25 Peer reviews
  20. 20. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 26 You’re not the only one who’s process is changing Lesson #2
  21. 21. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 27 Auditing No more code audits Everything in version control Mutation testing / test change approvals Enforced peer reviews Green goes to production Approvals in workflow
  22. 22. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 28 Regulatory conformity by design
  23. 23. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 29 Business IT antipatterns Fallback plans Manual Acceptance Testing Education for users User documentation Communication about releases @kimvanwilgen29
  24. 24. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 30 Releasenotes from jira
  25. 25. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 31 Agile Product management
  26. 26. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 32
  27. 27. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 33 Test automation requires architecture and design Lesson #3
  28. 28. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 34 Test pyramid Focus on small tests and fast feedback that’s valuable and supports you the most
  29. 29. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 35 Business users think about the user interface perspective. They offer examples on how things should work rather than what is required. This extra information must be removed to make key examples simple to communicate and understand. Refining the specification
  30. 30. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 36 Imperative vs. Declarative language And being unibiquitous
  31. 31. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 37 Collaboration of engineers and testers
  32. 32. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 38 Branching is your new mother-in-law: sometimes you have to go there but you never want to Lesson #4
  33. 33. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 39 Isolation and integration
  34. 34. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 40
  35. 35. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 41 Branch, blue/green Feature toggling Direct delivery by having no frontend Intensive customer collaboration and preacceptance The shipping delay pyramid
  36. 36. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 42 Customers don’t want continuous delivery Lesson #5
  37. 37. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 43 Insurance company Service provider Wholesale Agents ANVA Insurtech company for the Netherlands
  38. 38. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 44 Collaborate with users on test automation First improve, then accelarate Pull, not push Explain your goal Build trust
  39. 39. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 46 @kimvanwilgen | www.kimvanwilgen.com Closing down Keep going
  40. 40. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 47 @kimvanwilgen | www.kimvanwilgen.com References and questions www.kimvanwilgen.com kimvanwilgen kimvanwilgen@gmail.com

×