This document discusses continuous delivery and the missing parts of implementing it fully. It begins by defining continuous delivery as building, testing, and releasing software faster and more frequently. It outlines eight principles and four practices of continuous delivery. However, it notes that while developers may implement continuous delivery, the operations side is often missing parts like configuration management, immutable infrastructure, logging, metrics, monitoring, orchestration, and disaster recovery. A maturity model for continuous delivery is presented, and benefits like agility, faster recovery, more experimentation, and better products for customers are discussed.

1. Continuous Delivery - The
Missing Parts
Paul Stack
http://twitter.com/stack72
mail: paul@paulstack.co.uk

2. About Me
Infrastructure Engineer for a cool startup :)
Reformed ASP.NET / C# Developer
DevOps Extremist
Conference Junkie

3. Background to this talk

4. Continuous Delivery
…. is a set of practices and
principles aimed at, building,
testing and releasing software
faster and more frequently.

5. 8 principles of Continuous
Delivery
The process for releasing/deploying software MUST be repeatable
and reliable.
Automate everything!
If somethings difficult or painful, do it more often.
Keep everything in source control
Done means “released”
Build quality in!
Everybody has responsibility for the release process
Improve continuously

6. 4 Practices of Continuous
Delivery
Build binaries only once
Use precisely the same mechanism to deploy to every
environment
Smoke test your deployment
If anything fails, stop the line!

7. Has anyone read this book?

8. So continuous delivery is
only 5 years old??

9. Agile Manifesto
“Our highest priority is to satisfy the
customer through early and
continuous delivery of valuable
software"

10. Common Misconceptions

11. 1. Continuous Delivery is
something only startups can
achieve

12. 2. Continuous Delivery only
works for NodeJS / Ruby /
Go developers

13. 3. We can hire a consultant
to help us implement
‘Continuous Delivery’

14. 4. Right click and deploy in
your IDE is continuous
delivery

15. 5. Continuous delivery is as
simple as hooking github to
our Azure / Heroku
account…..

16. “Until your pretty code is in
production, making money, or doing
whatever it does, you’ve just wasted
your time”
Chris Read
@cread
#LondonCI

17. But haven’t I just
contradicted myself?

18. The traditional technical side
of a company
Developers
QA
SysAdmins
Network
Helpdesk
InfoSec
+ lots more

20. Aren’t we supposed to be
one team?

21. “How long would it take your
organisation to deploy a change that
involved just one single line of code?
Do you do this on a repeatable, reliable
basis?”
Implementing Lean Software Development
Mary Poppendieck

22. Value Stream Map

23. The Value Stream Map for
Ops is worse….

25. The rise of DevOps…..

27. October 30 - 31, 2009
Ghent, Belgium
Developers + System Administrators
for 2 days
= DevOpsDays

33. How does DevOps help
with this type of thing?

34. ‘The 3 ways’
• Systems thinking
• Amplify Feedback loops
• Culture of Continual
Experimentation and learning

35. The first way…

36. Understanding Work..
• Business Projects (search, UI improvements)
• Internal Projects (architecture changes)
• Changes (deployments, schema updates)
• Unplanned work (downtime, investigations)

37. The second way…

38. We found that when we woke developers up at 2am,
defects got fixed faster!
-Patrick Lightbody
CEO, Browsermob

39. The third way…

41. You can adopt DevOps
through….
Culture
Automation
Measurement
Sharing

42. We are *all* part of the same
team!

43. Metrics and Automation are
key!

44. The technical side of the
business post-DevOps….

46. The ops side of Continuous
Delivery

47. Configuration Management

48. Immutable Infrastructure

50. Immutable Infrastructure

51. Disposable Infrastructure

52. Logging

55. Metrics

57. Monitoring

59. https://github.com/stack72/nagios-elasticsearch

61. Orchestration

63. Data Center as Code?

67. Disaster Recovery?

69. The Continuous Delivery
Maturity Model

70. http://www.infoq.com/articles/Continuous-Delivery-Maturity-Model

71. The Benefits of Continuous
Delivery
• High Performing IT Teams are more
Agile!
• High Performing IT Teams can recover
faster!
• High Performing IT Teams can
experiment more!
https://puppetlabs.com/sites/default/files/2014-state-of-devops-report.pdf

72. Continuous Delivery means
better products for your
customers!*
* Customers can be internal or external

73. Questions?

74. Paul Stack
@stack72