This document discusses implementing continuous delivery practices at a bank. It outlines some of the challenges with legacy banking systems including old code, lack of agile processes, and heavy regulation. It then proposes adopting agile, software craftsmanship, and DevOps practices to automate releases, improve quality, and speed up delivery. Key aspects of the proposed continuous delivery program include adopting Scrum, test-driven development, infrastructure as code, automated deployments, and a cloud platform. The results were transforming over 400 applications to reduce time to market from months to weeks and deployment time from months to minutes.

1. Making a Mammoth
Run
Continuous Delivery in a bank

2. I am Laurent Grangeau
I love to automate things and run apps at scale.
You can find me at @laurentgrangeau
Hello!

3. Overview of
softwares in bank
industries1

4. Banking overview
Old code
There is lots of legacy code.
Generally, the code base is > 5
years old.
No agile process
Mostly waterfall process, ITIL
compliant.
Regulation
Banks can’t do what they want.
There is a lot of regulation and
audits.
Monolithic softwares
As softwares were designed
years ago, there is little
microservices, and no 12factor
principles.
Releases are manual
Generally, release is a manual
process with service
interruption.
Obsolete infrastructures
There are still mainframe
computers or specialized
appliances like Sparc
machines.

5. Fintechs arrival2

6. $12.7 billions funding
1.000+ companies
Leverage on cutting edge
technologies
Fintech landscape

7. Appears in 2008
$921 millions cumulative
investment
805 blockchain startups
$4.9 billions Bitcoin capitalisation
Blockchain ecosystem

8. Fintechs are taking
market shares…
It’s time to react !
BANKS
FINTECHS

9. Continuous
Delivery program3

10. Be like the GAFA
Be faster, bring more business value, reduce
maintenance costs

11. Why ?
◉ Faster time to market
=> Competitive advantage
◉ Better quality of product
=> Higher customer satisfaction
◉ Processes optimized
=> Reduced total cost of ownership

12. Change management
Agile coaches
Bring more business
value, involve
stakeholders.
ex. Scrum, Kanban,
Backlog grooming,
…
Software
craftsmanship
coaches
Build robust, testable
and sustainable
code.
ex. TDD, BDD,
Clean code, …
DevOps coaches
Automate the
delivery.
ex. IaC, Automated
deployment, …

13. Agile pillar
◉ What is Agile ?
◉ “Our highest priority is to satisfy the customer
through early and continuous delivery of
valuable software”
◉ Why ?
◉ Increase quality of delivery and reduce time to
market

14. Agile pillar
◉ Scrum/Kanban product backlog management
◉ Backlog grooming
◉ Story mapping
◉ Business analysts involved
◉ Iterative development
◉ Minimum viable product
◉ …

15. Have rapid feedback
Iterative development, deliver value to customers,
people collaboration, respond to change

16. Software craftsmanship pillar
◉ What is software craftsmanship ?
◉ “Any fool can write code that a computer can
understand.
Good programmers write code that human can
understand”
M.Fowler
◉ Why ?
◉ To add value and respond to change

17. Software craftsmanship pillar
◉ Test Driven Development
◉ Behavior Driven Development
◉ Clean code / architecture
◉ « Three amigos »
◉ Continuous integration / testing
◉ Testing and refactoring legacy code
◉ …

18. Software craftsmanship pillar
◉ Collaboration culture
◉ Coding dojos
◉ Hackathon / Coding games
◉ Meetup / Fair / Conference
◉ Blog
◉ Community projects
◉ …

19. Have better code quality
Collaboration culture, reduce maintenance costs,
improve reusability

20. DevOps pillar
◉ What is DevOps ?
◉ DevOps is a culture, movement or practice that emphasizes
the collaboration and communication of both software developers
and other information-technology (IT) professionals while
automating the process of software delivery and infrastructure
changes.
◉ Why ?
◉ To increase effectiveness, reduce TTM and implements
continuous improvement

21. DevOps pillar
◉ Dev / Ops collaboration
◉ Infrastructure as Code
◉ Automated deployment
◉ Metrology
◉ Release pipeline
◉ Desired state
◉ …

22. One team, everything automated
Continuous improvement, faster time-to-market,
faster resolution of problems, more stable
environment

23. Platform
Backlog
grooming
Development
interface
Source code
management
Continuous
integration
Testing
Libraries
repository
Deployment
automation
Metrology
Infrastructure as code

24.  400+ applications transformed
 Reduce TTM from months to 2
weeks
 Reduce deploy time from months
to minutes

25. What’s next ?4

26. New challenges
◉ Resiliency
◉ Scalability
◉ Infrastructure hybridation
◉ Multi-tenancy
◉ Opensource culture
◉ Service discovery
◉ Secret management

27. Cloud & PaaS program

28. Platform
Metrology
Backlog
grooming
Development
interface
Source code
management
Continuous
integration
Testing
Libraries
repository
Deployment
automation

30. Platform
Registry
Docker-swarm
The registrator
discovers new
containers and
feeds the registry

31. Platform
Docker-swarm

32. Service discovery
Registry
Service providerService consumer
1. Publish2. Find
3. Bind

33. Service discovery

34. Application K/V store
DEV STAGING PROD
K/V store K/V store
Update version

36. Password generation
On demand
credentials
No longer need
harcoded
credentials
1. Request credentials
2. Connect
3. Scale
4. Connect
Add
credentials

37. Impersonification
I want to
troubleshoot
problems
Production
Works for SSH and DB !
1. Request credentials
2. Generate access
3. Login with generated credentials
Dev

38. PKI : certificates generation
Host Host Host
Generating
on demand
certificates
for containers
communication
Request certificates

39. Conclusion6

40.  Continuous delivery is now complete
part of the bank
 Huge change on the manner of working
 Nearly everything is automated

41. Any questions ?
You can find me at
◉ @laurentgrangeau
◉ laurent.grangeau@gmail.com
Thanks!