This document discusses overcoming impediments to continuous delivery. It identifies key impediments as people, infrastructure, software products, and complexity. The document emphasizes establishing configuration management, treating infrastructure as code, and automating delivery pipelines to enable continuous delivery. Integrated pipelines that bring together CI and integration testing are recommended to help overcome impediments.

1. Overcoming Impedance
to Continuous Delivery
Mark Rendell
mark.rendell@accenture.com
@markosrendell
http://markosrendell.wordpress.com

2. @markosrendell 2
Agenda
• What is Continuous Delivery?
• Why would you want it?
• What do we have to get right?
• Impedance: People
• Impedance: Infrastructure
• Impedance: Software Products
• Impedance: Complexity

3. @markosrendell 3
What is Continuous Delivery?
An approach to industrialising your delivery

4. @markosrendell 4
What is Continuous Delivery?
http://markosrendell.wordpress.com
A focus on Flow

5. @markosrendell 5
Why would you want continuous delivery?
Happiness through a happy organisation

6. @markosrendell 6
Continuous Delivery Essentials
Part 1: rock solid holistic Configuration Management

7. @markosrendell 7
Continuous Delivery Essentials
Part 2: Platform treated as an Application (PaaA)

8. @markosrendell 8
Continuous Delivery Essentials
Compile
and package
Static Code
Analysis
Unit Tests
Run Functional
Tests
Run Security
Tests
PT env deploy
Run Tech
Tests
CT env
deploy
Production
deploy
Check
in
Part 3: Automated Delivery Pipeline

9. @markosrendell 9
Continuous Delivery Essentials
Compile
and package
Static Code
Analysis
Unit Tests
Run Functional
Tests
Run Security
Tests
PT env deploy
Run Tech
Tests
CT env
deploy
Production
deploy
Check
in
Compile
and package
Static Code
Analysis
Unit Tests
Run Functional
Tests
Run Security
Tests
PT env deploy
Run Tech
Tests
CT env
deploy
Production
deploy
Check
in
Compile
and package
Static Code
Analysis
Unit Tests
Run Functional
Tests
Run Security
Tests
PT env deploy
Run Tech
Tests
CT env
deploy
Production
deploy
Check
in
Compile
and package
Static Code
Analysis
Unit Tests
Run Functional
Tests
Run Security
Tests
PT env deploy
Run Tech
Tests
CT env
deploy
Production
deploy
Check
in
Compile
and package
Unit Tests
Platform env
deploy
Monitoring
tests
Check
in
Compile
and package
Unit Tests
Platform env
deploy
Monitoring
tests
Check
in
Compile
and package
Unit Tests
Platform env
deploy
Monitoring
tests
Check
in
Compile
and package
Unit Tests
Platform env
deploy
Monitoring
tests
Check
in
Compile
and package
Unit Tests
Platform env
deploy
Monitoring
tests
Check
in
Platform
Part 3: Automated Delivery Pipeline

10. @markosrendell 10
All too familiar?
Version ???
Compile
and package
Static Code
Analysis
Unit Tests
Run Functional
Tests
Run Security
Tests
PT env deploy
Run Tech
Tests
CT env
deploy
Production
deploy
Check
in
COTSInfrastructureESB
Package
Static Code
Analysis
Unit Tests PT env deploy
Production
deploy
CT env
deploy
Check
in
Package Unit Tests
CT env
deploy
Production
deploy
PT env deployCheck
in

11. @markosrendell 11
Impedance: People
Ignorance? Ambivalence?

12. @markosrendell 12
Impedance: People
Obedience? Disobedience?

13. @markosrendell 13
Impedance: People and Governance
Who “owns” these lovely things?

14. @markosrendell 14
Dev Ops
UI
agency
Cloud
“Ops”
(possibly
shadow!)
Traditional
operations
“Heritage
System”
owner
Mobile
partners
ERP owner CMS
vendor
CRM
owner
SaaS
(possibly
shadow!)
“Operations”
Impedance: People and Organisational Complexity
Get a DevOps team if that helps you

15. @markosrendell 15
Impedance: Infrastructure
Best infrastructure team quarter ever – no new servers given out?

16. @markosrendell 16
Impedance: Infrastructure
Demand “public cloud” equivalent levels of capability and service (or use public cloud!)

17. @markosrendell 17
Impedance: Infrastructure Code quality
Infra-as-code == Infra-is-code {
Give it the Jenkins treatment!
}
e.g. MySQL
Chef cookbook
e.g. RabbitMQ
Bosh release
Treat you Platform as an Application and engineer it accordingly

18. @markosrendell 18
Impedance: Software Products
Tame the COTS products – it IS possible!
Build
Static Code
Analysis
Deploy
Code
Load Test
Data
Run Test
Harness
Deploy
Code
SCM Repo

19. @markosrendell 19
Impedance: Software Products
Tame the COTS products – it IS possible!
Build
Static Code
Analysis
Deploy
Code
Load Test
Data
Run Test
Harness
Deploy
Code
SCM Repo
Plain text
(easy)
Anything
you like!
Native
concept
SonarQube
PMD
Checkstyle
Findbugs
Lint
FxCop
etc.
Options,
options,
options
...
etc.

20. @markosrendell 20
Impedance: Software Products
Tame the COTS products – it IS possible!
Build
Static Code
Analysis
Deploy
Code
Load Test
Data
Run Test
Harness
Deploy
Code
SCM Repo
Binary or
proprietary
XML
Can you
even
flatten
CLI?
Headlless
IDE
Write your
own
CLI? etc.

21. @markosrendell 21
Impedance: Complexity
Have a strategy for tracking component integration

22. @markosrendell 22
Integrated Pipelines
CI pipelines
Integrated pipelines work really well

23. @markosrendell 23
Integrated Pipelines
CI pipelines
Integration pipeline
Integrated pipelines work really well

24. @markosrendell 24
Got for it!
mark.rendell@accenture.com
@markosrendell
http://markosrendell.wordpress.com