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.
Upcoming SlideShare
What to Upload to SlideShare
Next
Download to read offline and view in fullscreen.

1

Share

Download to read offline

20180509 (codemotion) continuous delivery

Download to read offline

Continuous delivery in 10 easy mistakes, and how to do better.

With agile principles and practices reaching maturity, in many organizations the focus for the coming years will be on the next steps. Beyond agile. In fast pace organizations are adopting agile, DevOps, continuous delivery and new architectures such as microservices. Often all at once. Although from a perspective of similarities between these paradigms this makes sense, this also is a recipe for failures and hard lessons to be learned. Kim van Wilgen will share her experiences from the pipeline to the enterprise level and from failure to success.

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

20180509 (codemotion) continuous delivery

  1. 1. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Continuous delivery in 10 easy mistakes, and how to do better Kim van Wilgen AMSTERDAM | MAY 8-9, 2018
  2. 2. About me Kim van Wilgen Head of development at ANVA Former head of IT at Klaverblad Business background Managing since 2005 Programming since 2018 @kimvanwilgen nl.linkedin.com/kimvanwilgen kimvanwilgen@gmail.com www.kimvanwilgen.com
  3. 3. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Insurance company Service provider Wholesale Agents ANVA Insurtech company for the Netherlands
  4. 4. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Software development is complex
  5. 5. Large projects 10% success 52% challenged Small projects 74% success 22% challenged From: the Chaos manifesto 2013, The Standish group
  6. 6. Unused features Large deliveries 64% Small deliveries 14% From: the Chaos manifesto 2013, The Standish group
  7. 7. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes @kimvanwilgen | www.kimvanwilgen.com How to deliver continuous delivery In 10 lessons
  8. 8. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Automate delivery
  9. 9. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes 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
  10. 10. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes What is continuous? Naming continuous to be a problem Amazon ANVAANVA KlaverbladKlaverblad
  11. 11. Tool focused On the side No vision or requirements
  12. 12. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Results • Daily delivery • Shifting culture • Incomplete tests • No compliance or control • No monitoring
  13. 13. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Continuous delivery means you’re building software. So treat is as a software development process
  14. 14. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Have a backlog and define your minimal products
  15. 15. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes 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,metrics and visibility Add monitoring Add reviews
  16. 16. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Build status
  17. 17. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Issue tracking
  18. 18. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Design for fast feedback and evolution
  19. 19. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes 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
  20. 20. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Test pyramid reinvented Small tests and risk based
  21. 21. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Maintainable tests And living documentation
  22. 22. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Branching is your new mother-in-law: sometimes you have to go there but you want to minimize it
  23. 23. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Branching Feature flags No frontend Co-creation and pre-acceptance The shipping delay pyramid
  24. 24. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Acceptance by team Rehearsal Canary production Global production Release strategy Feature flags Sustainable pace Shipping delay Impact reduction
  25. 25. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Speed of delivery isn’t the answer to life, the universe and everything.
  26. 26. Continuous security DIY hacking Integration in the pipeline Secure coding
  27. 27. Auditing and compliance Everything in version control Test change approval Enforced peer reviews Green goes to production Approvals in workflow Conformity by design
  28. 28. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Reinvent implementation and assistance 6
  29. 29. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Fallback plans Manual Acceptance Testing Education for users User documentation Communication about releases Asking feedback Canary releasing Cocreating tests Walkthroughs Embedded user assistance and chatbots Release notes integrated in deployment Monitoring feedback Business IT antipatterns @kimvanwilgen37
  30. 30. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes You’re only as small as your MVP and as agile as your roadmap
  31. 31. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Stop extensive planning
  32. 32. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Product vision and business cases
  33. 33. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Go with the flow
  34. 34. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes The red sprint antipattern “Sprints won’t increase speed, they will just make people unhappy” – Sander Hoogendoorn http://sanderhoogendoorn.com/blog/index.php/burn-down- or-burn-out/
  35. 35. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes No estimates movement “No estimates doesn’t mean no estimates” – Seb Rose
  36. 36. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Start looking at goals and results
  37. 37. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Only autonomy scales
  38. 38. Team autonomy asks leaders to change
  39. 39. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Autonomy can’t exist without transparancy
  40. 40. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Customers don’t want continuous delivery 10
  41. 41. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Legacy code and broken trust
  42. 42. Explain your goal Pull, not push First improve, then accelarate
  43. 43. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes Be ready for surprises
  44. 44. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes @kimvanwilgen | www.kimvanwilgen.com Closing down Keep going
  45. 45. @kimvanwilgen | www.kimvanwilgen.comContinuous delivery in 10 easy mistakes @kimvanwilgen | www.kimvanwilgen.com References and questions www.kimvanwilgen.com kimvanwilgen kimvanwilgen@gmail.com
  • MarcoBrundel

    May. 10, 2018

Continuous delivery in 10 easy mistakes, and how to do better. With agile principles and practices reaching maturity, in many organizations the focus for the coming years will be on the next steps. Beyond agile. In fast pace organizations are adopting agile, DevOps, continuous delivery and new architectures such as microservices. Often all at once. Although from a perspective of similarities between these paradigms this makes sense, this also is a recipe for failures and hard lessons to be learned. Kim van Wilgen will share her experiences from the pipeline to the enterprise level and from failure to success.

Views

Total views

310

On Slideshare

0

From embeds

0

Number of embeds

9

Actions

Downloads

4

Shares

0

Comments

0

Likes

1

×