The document discusses the three pillars of continuous delivery as culture, practices, and tooling. It states that culture is expressed through practices which are carried out using tools. However, when first starting a continuous delivery program, it is better to focus on practices and tools first before culture in order to get quick wins. Implementing practices and tools can help bootstrap a culture over time through communicating successes. The document provides examples of practices and tools as well as tips for getting started with continuous delivery.

1. Three Pillars of Continuous Delivery:
Culture, Practices & Tooling
Andrew Phillips, XebiaLabs

2. About Me
o
VP Products for XebiaLabs
o
Lots of enterprise software development on
high-performance systems
o
Been on both sides of the “Dev…Ops”
fence
o
Active open source contributor and
committer:
jclouds, Akka, Gradle and others
o
Cloud, PaaS & JVM language fan (mainly
Scala, Clojure)
o
Regular meetup, conference etc. presenter

3. About Me
o
VP Products for XebiaLabs
o
Lots of enterprise software development on highperformance systems
o
Been on both sides of the “Dev…Ops” fence
o
Active open source contributor and committer:
jclouds, Akka, Gradle and others
o
Cloud, PaaS & JVM language fan (mainly Scala,
Clojure)
o
Regular meetup, conference etc. presenter

4. About XebiaLabs
o
Leading provider of delivery
automation software focused on
helping companies deliver higher
quality software faster.
o
Reduce development applications
costs
o
Accelerate application time to market
o
Bridge the gap between
Development and Operations
Global Customers, Global Success
and many more…

5. Agenda
o Lightning Continuous Delivery
Recap
o Tooling, Practices, Culture…how do
they relate?
o Bootstrapping a CD Culture
o Crossing “Quick Win Chasm”
o Practical Examples
o Getting Started

6. What Is Continuous Delivery?
“Continuous delivery is a set of patterns and
best practices that can help software
teams dramatically improve the pace and
quality of their software delivery.”

7. Why Continuous Delivery?
o Competitive pressure
o Hot trend
o Clear business values
o Accelerate time to market
o Increase application quality
o Increase customer
responsiveness

8. Why Continuous Delivery?

9. Aside 1: Continuous Delivery & Agile
“Continuous Delivery is a set of patterns and
best practices that can help software
teams dramatically improve the pace and
quality of their software delivery.”

10. Aside 1: Continuous Delivery & Agile
“Our highest priority is to satisfy the
customer through early and continuous
delivery of valuable software.”

11. Aside 1: Continuous Delivery & Agile

12. Aside 1: Continuous Delivery & Agile
“Our highest priority is to satisfy the
customer through early and continuous
delivery of valuable software.”
Principle #1 from the Agile Manifesto

13. Aside 2: Continuous Delivery & Devops
o Flood of overlapping messaging in
this space right now
o Analysts and new vendors piling on
to the bandwagon
o Rather difficult to parse it all at
present, especially if you’re coming
at this now

14. Aside 2: Continuous Delivery & Devops
o Flood of overlapping messaging in this
space right now
o Analysts and new vendors piling on to
the bandwagon
o Rather difficult to parse it all at present,
especially if you’re coming at this now
o Key point: Whatever you call it, make
sure you have some defined goals that
are intended to provide some
measurable business value
o Happy to debate and discuss
definitions over lunch!

15. Three Pillars
" Culture: set of values,
beliefs and traditions
" Practices: behaviours and
actions that derive from
these values and beliefs
" Tooling: instruments used
to carry out the
behaviours and actions

16. Three Pillars
Culture
is expressed through
Practices
carried out using
Tooling

17. Three Pillars

18. A Bit About Culture
o Once it’s reached a cultural level:
extremely resilient to problems
o If the tooling breaks, people will fix it
o Internal motivation to carry out the
practices and make them work
o (Risk of groupthink, so tolerance of
open minds is important
o Something for a lunchtime
discussion)

19. A Bit About Culture
o Problem: culture is hard to impose
from the top down
o Look at history!
o And most organizations are not at
the point where a culture is in place
o They’re just starting out on their
CD journey!
o So...what can we do about this?

20. Bootstrapping a CD Culture
o Let’s look at those three
pillars a different way

21. Bootstrapping a CD Culture
Culture
is expressed through
Practices
carried out using
Tooling

22. Bootstrapping a CD Culture
Culture
is expressed through
Practices
carried out using
Tooling

23. Bootstrapping a CD Culture
Culture
whose effects give rise to
Practices
enables
Tooling

24. Bootstrapping a CD Culture
o Key point here: inverting the causal
relationships!
o Why start with tooling & practices?

25. Bootstrapping a CD Culture
o Easy to get up and running
o Certainly compared to culture!
o Low risk
o Largely free or low-cost tools
o “Skunkworks-able”
o Quick, demonstrable effects
o Go after the low hanging fruit!

26. “Quick Win Chasm”
o A story…
o ACME Inc. has heard of this
amazing tooling that can help
automate their software delivery
process
o Consultants come in a build a
delivery pipeline
o Runs fine for a while
o Not easy to adapt to new projects,
as the consultants have moved on
o Then some parts of the pipeline start
to fail, and are switched off or
bypassed
o …

27. “Quick Win Chasm”
o Lesson: Tooling by itself only goes so
far
o Even if it’s very reliable!
o Resilience comes from making this
part of your DNA
o This Is Not Easy!
o Especially since the temptation is
to see the initial improvements
and stop there

28. Crossing Quick Win Chasm
o Five key points
o Get management buy in
o Find someone who’s “been
there”
o Create champions
o Make things visible
o Communicate,
communicate,
communicate

29. Let’s Get Practical
o Tooling
o Code review

30. Let’s Get Practical
o Tooling
o Code review
o Continuous Integration

31. Let’s Get Practical
o Tooling
o Code review
o Continuous Integration
o Deployment

32. Let’s Get Practical
o Tooling
o Code review
o Continuous Integration
o Deployment
o Testing & quality

33. Let’s Get Practical
o Tooling
o Code review
o Continuous Integration
o Deployment
o Testing & quality
o Provisioning

34. Let’s Get Practical
o Tooling
o Code review
o Continuous Integration
o Deployment
o Testing & quality
o Provisioning
o Orchestration

35. Let’s Get Practical
o Tooling
o Code review
o Continuous Integration
o Deployment
o Testing & quality
o Provisioning
o Orchestration
o Monitoring

36. Let’s Get Practical
o Practices
o Keep changes small

37. Let’s Get Practical
o Practices
o Keep changes small
o Quality before functionality

38. Let’s Get Practical
o Practices
o Keep changes small
o Quality before functionality
o Put the test up front

39. Let’s Get Practical
o Practices
o Keep changes small
o Quality before functionality
o Put the test up front
o Everyone involved early

40. Let’s Get Practical
o Practices
o Keep changes small
o Quality before functionality
o Put the test up front
o Everyone involved early
o No more (code) than necessary

41. Let’s Get Practical
o Practices
o Keep changes small
o Quality before functionality
o Put the test up front
o Everyone involved early
o No more (code) than necessary
o Ongoing user dialog

42. Let’s Get Practical
o Practices
o Keep changes small
o Quality before functionality
o Put the test up front
o Everyone involved early
o No more (code) than necessary
o Ongoing user dialog
o Delivery tooling = serious tooling

43. Let’s Get Practical
o Culture
o We can always do better

44. Let’s Get Practical
o Culture
o We can always do better
o Our service, our features,
our users

45. Let’s Get Practical
o Culture
o We can always do better
o Our service, our features,
our users
o ‘Us’ includes the business

46. Let’s Get Practical
o Culture
o We can always do better
o Our service, our features,
our users
o ‘Us’ includes the business
o Tools work for the team

47. Let’s Get Practical
o Culture
o We can always do better
o Our service, our features, our
users
o ‘Us’ includes the business
o Tools work for the team
o Nobody goes home if the
build delivery system is
broken

48. Getting Started
o Get a baseline: Value Stream
Analysis
o Open mind: We Can Do Things
Differently
o Define incremental goals
o No Ocean Boiling!
o Start with tooling
o Go after low-hanging fruit

49. Getting Started
o Testing and quality
o More investment and backfilling
required
o Requires buy-in
o Adapt your architecture to allow for
smaller changes
o Greenfield? Lucky you!
o Otherwise, will need to tackle this
eventually
o Full-time business focus
o It’s about putting the business at the
wheel!
o Often need some persuasion to
actually drive…

50. More Info
More Information
www.xebialabs.com
blog.xebialabs.com
Get Started
www.xebialabs.com/trial
Stay Informed
ww.linkedin.com/company/xebialabs
@xebialabs

51. Get In Touch!
o Andrew Phillips
aphillips at xebialabs dot com
o Talk over lunch or at the XebiaLabs table
o Don’t forget to stop by the XebiaLabs &
Cachet Software tables for more
information (& swag)

52. Get In Touch!
o Andrew Phillips
aphillips at xebialabs dot com
o Talk over lunch or at the XebiaLabs table
o Don’t forget to stop by the XebiaLabs &
Cachet Software tables for more
information (& swag)

53. Thank you!