A way to continuous delivery

It has been said that Scrum doesn’t fix problems, it just makes them visible. Fixing the problems is the responsibility of the team. If you don’t have interest in solving the problems, Scrum just causes you pain without benefit. Continuous delivery is similar.

The talk will go through the pains encountered and reliefs implemented by a team aiming for continuous delivery. Many of the implemented practices are valuable on their own but continuous delivery brings the pain so visible it can’t be ignored. We will also go through concrete tools used to accelerate the process towards faster feedback, confidence and predictability given by continuous delivery.

Transcript

1. A way to continuous delivery Continuous delivery seminar 2.12.2014 Vesa Vänskä, Kisko Labs
2. Continuous integration, delivery & deployment Terms
3. • Continuous integration
 • Continuous delivery
 • Continuous deployment
4. Scrum & Continuous Delivery
5. Where I’m coming from Background
6. Web tools for professionals.
7. • 50/50 designer/developer
 • Ruby on Rails
 • SaaS & PaaS
8. • Partner of the company
 • Keep the technology side of our projects excellent
9. Our path to continuous delivery
11. From Nebula to Heroku
13. Continuous integration server
15. Alerting
16. Monitoring
19. • Automation
 • Everything under version control • Hosted platforms • Open-source • Cross-service integration • Visibility
20. Pain
21. • Don't brush it off
 • Listen to your pain
 • Let it guide you
22. "... broke again!"
23. "Why do we always ...?"
24. "I waste time on this on every project"
25. • A er you've become conscious of the pain
 you can try to remove the source of it
 • Learning new techniques, languages and tools
 makes you discover new pains
 • Life will never be pain free so why not use it 
 as a valuable tool
26. • Heroku was relief to the pain of not having automated server administration
 • Monitoring was relief to the pain of not having visibility
 • Moving alerting from email to a centralized system was also relief to the lack of visibility
 • Continuous integration server was the relief for not having certainty
27. Future
28. "The future is already here — it's just not very evenly distributed."
29. • Need for faster feedback, confidence and predictability is always there
 • Tools are ge ing be er everywhere
 • For us: automatic deployment to staging
30. • Currently proprietary platforms are ahead
 • Self-hosted and open-source solutions will get there
 • I see this as the way most services should be built and run in the future
31. • Cultures will change
 • From Hollywood launches to more incremental and iterative approach
 • Feature flags, stealth launches, deploying the backend first…
32. TODO
33. • What is the most painful part of your system and how could your team
 minimize that pain?
 • Did I talk about a technology or process unknown to you? Take 15 minutes tomorrow and investigate it.
 • Is there a blocker for implementing one of the continuous integration practices? Can that be solved?
34. h p://martinfowler.com/delivery.html
35. Thank you! Email: vesa@kiskolabs.com Twi er: @vesan