The document discusses the importance of continuous delivery in software development, emphasizing customer satisfaction through early and reliable releases. It highlights benefits such as faster time to market, improved product quality, and user feedback. Best practices for delivery include automation, consistent deployment, and the implementation of DevOps principles.

1. HELPING CLIENTS REACH THEIR GOALS WITH
THE LATEST TECHNOLOGIES

2. Continuous Delivery
Ibon Landa
Plain Concepts

3. ilanda@plainconcepts.com
@ibonilm
http://geeks.ms/blogs/ilanda

4. Info@plainconcepts.com
Nervión 3, Planta 6
48001 Bilbao
+34 94 6008 168
Bilbao

5. Our highest priority is to satisfy the customer
through early and continuous delivery of
valuable software.
Principles behind the Agile Manifesto

6. How long would it take your
organization to deploy a
change that involves just one
single line of code?
Do you do this on a
repeatable, reliable basis?
Mary & Tom Poppendieck
Implementing Lean Software Development

7. Done means "released". This implies
ownership of a project right up until it’s in the
hands of the user, and working properly.
There’s none of this "I’ve checked in my code
so it’s done as far as I’m concerned".
James Betteley

8. Las entregas van a ir guiadas por
las necesidades de negocio, no
por las restricciones
operacionales.

9. Why Continuous Delivery?
• Accelerated Time to Market
• Reduces the need for large capital investments
• Building the Right Product
• Improved Productivity and Efficiency
• Reliable Releases
• Improved Product Quality
• Improved Customer Satisfaction
• Earlier feedback from users on each new feature

10. SOFTWARE
DELIVERY
MODELS

11. #1: No model, or random delivery.

12. #2: Let the operations guys figure out.

13. #3: Defined and collaborative approach.

14. DELIVERY PRACTICES

15. Version
everything

16. Automate
everything

17. Tokenize
configurations

18. Use one-click deployments

19. Deploy to a copy of
production

20. Deploy the same way to every
environment

21. Have always a rollback
mechanism in place.

23. Lock down
the environments.

24. Build
only
once

25. Measure the delivery process

26. Bring the pain forward

27. Build a release pipeline

28. Practice
DevOps!

29. THANKS!