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.

20171116 (buildstuff) the continuous culture

836 views

Published on

The continuous culture at Buildstuff Vilnius

Published in: Engineering
  • Be the first to comment

  • Be the first to like this

20171116 (buildstuff) the continuous culture

  1. 1. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 1 The continuous culture
  2. 2. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 2 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 About me
  3. 3. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 3 The continuous culture
  4. 4. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 4 Insurance company Service provider Wholesale Agents ANVA Insurtech company for the Netherlands
  5. 5. @aahoogendoorn | www.ditisagile.nlDesigning, developing, testing and deploying microservices 5 @kimvanwilgen | www.ditisagile.nl Going faster Keeping up with competition
  6. 6. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 7 Software development is complex
  7. 7. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 8 Build up value and reduce risk The value of incremental change
  8. 8. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 9 Small projects vs. Large projects From: the Chaos manifesto 2013, The Standish group
  9. 9. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 10 Feedback and data grow value and innovation The value of incremental change
  10. 10. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 11 Building the right thing Having 14% vs 64% unused features
  11. 11. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 12 Innovation is not an epiphany, it’s exploration
  12. 12. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 13 Flow eliminates waste and overhead The value of incremental change
  13. 13. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 14 Flow provides insight Or at least enough of it
  14. 14. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 15 @kimvanwilgen | www.kimvanwilgen.nl How to deliver incremental change In 10 lessons
  15. 15. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 16 Be able to safely and sustainably deliver software to enable experiments
  16. 16. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 17 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
  17. 17. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 18 What is continuous Klaverblad ANVA ANVA Klaverblad Amazon
  18. 18. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 19 Tool focused No requirements or product vision Distributed over teams Besides other projects So let’s go
  19. 19. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 20 @kimvanwilgen | www.kimvanwilgen.com Results Incomplete tests No shipping choice No monitoring No compliance or control
  20. 20. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 21 Continuous delivery means you’re building software. So treat is as a software development process
  21. 21. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 22 Have a backlog and define your MVP
  22. 22. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 23
  23. 23. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 24 Level 1 Dev Test 1 Test n Integration Acceptance Production Dev Test 1 Test n For each component Full landscape Integration Scenario / UI testing Acceptance Production Add tests and metrics Add monitoring Add reviews
  24. 24. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 25 Improve and maturize by priority Quality Security Performance Mutation Experimenting A/B testing Canary releasing Blue / green deployments Data driven decisions Assistance Walkthroughs Chatbots Distributed releasing Health Issue tracking Build status Monitoring Immutable servers
  25. 25. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 29 You’re only as small as your MVP and as agile as your roadmap
  26. 26. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 30 Stop extensive planning
  27. 27. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 31 And stop red sprints
  28. 28. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 32 Agile Product management
  29. 29. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 33 Product vision and business cases
  30. 30. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 34 You’re not the only one who’s process is changing
  31. 31. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 35 Auditing and compliancce Everything in version control Mutation testing / test change approvals Enforced peer reviews Green goes to production Approvals in workflow Conformity by design
  32. 32. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 36 Business IT antipatterns Fallback plans Manual Acceptance Testing Education for users User documentation Communication about releases @kimvanwilgen36
  33. 33. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 37 Releasenotes from jira
  34. 34. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 38 Old school HR, management and functions undermine autonomy. Reinvent them
  35. 35. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 39
  36. 36. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 40 Inspiration over management
  37. 37. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 41 Feedforward Integration with each iteration for continuous flow Stakeholder input For acceptance and selfcritism Feedback for improvement of the team Supportive feedback for help with patterns or goals
  38. 38. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 42 Start looking at results
  39. 39. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 43 Feedback fun
  40. 40. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 44 Autonomy means trusting and giving space
  41. 41. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 45 Team autonomy asks leaders to change
  42. 42. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 46 Learning to learn
  43. 43. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 47 Learning cool new stuff everyday
  44. 44. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 48 Continuous learning
  45. 45. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 49 Discover together and celebrate new knowledge Learn to explore
  46. 46. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 50 Academy, workshops, hackatons, conferences
  47. 47. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 51 Design for fast feedback and evolution
  48. 48. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 52 Microservices are the first architectural style to fully embrace continuous delivery. It is an evolutionary architecture, which supports incremental non- breaking change as a first principle along multiple dimensions at the structural level of the application Neal Ford, Thoughtworks
  49. 49. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 53 Test pyramid Small tests and risk based
  50. 50. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 54 Maintainable tests And living documentation
  51. 51. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 55 Branching is your new mother-in- law: sometimes you have to go there but you want to minimize this
  52. 52. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 56 Isolation and integration
  53. 53. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 57
  54. 54. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 58 Branching Feature toggling No frontend path Co-creation and pre-acceptance The shipping delay pyramid
  55. 55. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 59 Customers don’t want continuous delivery
  56. 56. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 60 Legacy code and broken trust
  57. 57. @kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 61 Collaborate with users on test automation First improve, then accelarate Pull, not push Explain your goal Build trust
  58. 58. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 62 Continuous culture Continuous delivery Agile product development Learning organisation Agile HR Autonomous teams Microservices Enable rapid prototyping Do small experiments to seek value Enable learning from experiments Enable an evolutionary architecture Empower teams to decide and adapt fast Support people to learn agility and improve in their capabilities
  59. 59. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 63 Be ready for surprises
  60. 60. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 64 @kimvanwilgen | www.kimvanwilgen.com Closing down Keep going
  61. 61. @kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 65 @kimvanwilgen | www.kimvanwilgen.com References and questions www.kimvanwilgen.com kimvanwilgen kimvanwilgen@gmail.com

×