Like most major financial services companies, Stater is highly focused on evolving their business to be as customer-facing and as digital as possible. To get there, Stater has a bold vision: to deliver what takes their competitors weeks, in less than an hour. Attend and discover how Stater came to the realization that Continuous Delivery was the only way to get there.

1. Your Presenters
Andrew Phillips
VP DevOps
strategy for
XebiaLabs
▪ Lots of enterprise software development on
high-performance systems
▪ Been on both sides of the “Dev…Ops” fence
▪ Active open source contributor and committer
▪ Regular meetup, conference etc. presenter
Ton Kueter
Manager IT
Development for
Stater
▪ Background in lean and operations
▪ Background in financial services
▪ Responsible for CD implementation at Stater

2. Agenda
▪ Housekeeping
▪ Introduction Stater
▪ Stater’s Challenge
ü Agile development
ü Continuous Delivery
▪ What’s next
▪ Questions

3. Housekeeping
This webinar is being recorded
Links to the slides and the recording will be made available after the
presentation
You can post questions via the GoToWebinar Control Panel

4. Continuous Delivery by Stater
Ton Kueter
(Manager IT development)

5. www.stater.nl
5

6. Marketshare
6
§ Market share start 2014: 30%

7. Marketshare
7
§ Market share at start of 2014: 30%
§ Market share Q1 2015: 40%

8. Marketshare
8
§ Market share at the start of 2014: 30%
§ Marktet share Q1 2015: 40%
§ Goal: 70 % market share by the end of 2018

9. Innovation
99
E-Consumer
Financial agreement
Quick security for the
consumer
Accello
EXECUTION
ONLY
Bouwdepot
Mijn gegevens
Construction
App
E-Notary

10. 3 pillars for growth
10
70% market share
New
customers
Expanding
BPO offering
(mid office) Innovation
(digitalization)

11. Our IT landscape
11

12. Our challenges
§ Dissatisfied customers
§ Unstable testing environments
§ Painful releases
§ System outages
§ Incidents

13. Our plan
13

14. § Double checking
§ Fewer releases
§ More code bases for important projects
2. Improve delivery

15. That was “old school” and just not enough

16. How did we start?
16

17. How did we start?

18. Deep dive results
18
1) A lot of manual labour
2) Many windows
3) Integration problems
4) Waterfall

19. The answer: Continuous Delivery
Ontwikkel
Omgeving
Test
Omgeving
Acceptatie
Omgeving
Productie
Omgeving
Automated provisioning
Agile software
development
Continuous integration Automated testing
Automated deployment
19

20. CD technology stack
20

21. Easy does it: automated flows for releases
21

22. Build monitors for real time insights
22

23. Maturity matrix
Maturity
23

24. Speed…
24
Deliver test environment from1-2 weeks to 1 hour
Provisioning of servers from 1-2 days to 30 minutes
Deploying software from 1-2 weeks to 30 minutes
Integration from 2 months to 30 minutes
Automated test coverage from 0% to 70%

25. Sustaining the new way of working
25
Continuous
Integration
Team
Capabilities
Sub
category Assessment
criteria
Branches Team
werkt
op
de
TRUNK 63%
Branches Er
zijn
geen
project/RFC/feature-­‐branches
meer 25%
Omgevingen Team
werkt
op
de
centrale
AuTO
omgeving 38%
Omgevingen Team
heeft
geen
eigen
omgeving
meer 50%
Versiebeheer Team
checkt
werk
alvorens
in
te
checken
in
versiebeheer 100%
Versiebeheer Team
commit
vaak
en
vroegtijdig
(minimaal
dagelijks) 75%
Versiebeheer Team
zorgt
dat
commits
tussen
MidOffice,
Interfaces,
BackOffice
en
Databases
op
elkaar
afgestemd
zijn 88%
Versies Alle
opleveringen
zijn
uniek
en
traceerbaar 88%
Groene
builds Team
neemt
verantwoordelijkheid
bij
falende
build 75%
Groene
builds Team
voert
actief
root
cause
analysis
uit
bij
falende
build 63%
Groene
builds Ontwikkelaars
in
het
team
hebben
de
Jenkins
notifier
geïnstalleerd 38%
Groene
builds Er
is
een
grote,
centrale
build
monitor
in
de
buurt
van
ieder
team 88%
Groene
builds Team
acteert
op
negatieve
resultaten
op
de
build
monitor 38%
Code
quality Team
hanteert
Sonar
en
bijbehorende
standaarden 50%
Code
quality Team
draagt
verbeteringen
voor
Sonar
standaarden
aan
bij
Competence
Team 63%
Database Database-­‐scripts
worden
gedurende
de
sprint
uitgeleverd
in
versiebeheer 88%
Unit
Tests Unit
tests
worden
gelijktijdig
geschreven
wanneer
de
code
geschreven
wordt 75%
Unit
Tests Unit
tests
zijn
geautomatiseerd
en
onafhankelijk
van
andere
systemen 63%
Unit
Tests Unit
tests
zijn
geautomatiseerd
en
onafhankelijk
van
andere
code 63%
Unit
Tests Alle
ontwikkelaars
in
het
team
weten
hoe
ze
een
goede
unit
test
moeten
schrijven 75%
Unit
Tests Er
wordt
gebruik
gemaakt
van
Stubs,
Mocks
en/of
Fakes 75%
Unit
Tests Het
verschil
tussen
Stubs,
Mocks
en
Fakes
is
bij
het
hele
team
bekend 25%

26. Paradigm shift
26
§ Release more often
§ Use tools that best fit the job
§ Fewer code bases
§ Automate repetetive tasks

27. And now the team…
We sell projects, fixed scope, fixed time, fixed price
Very clear scope
Tooling: open source tooling, will fix every problem
Project name: Automation of test environments in stead of implementation
CD
We focused on the impact on to organizational structure right at the start
27

28. Agile software development
§ Stable teams instead of 1 person in 5 projects
§ Gap IT development and IT operations -> DEVOPS
§ Many windows in IT Operations:
§ IAAS
§ PAAS
§ SAAS
§ Special team for incidents -> “Eat your own dogfood”

29. Feature vs Component teams
29

30. Requirements
Design
Develop
Test
IT
Proces
implementa7on
Test
business
IT
Opera7ons
Sales/Ops
AgileTeamProduct Owner
BASIC
AGILE
IMPLEMENTATION
Requirements
Design
Develop
Test
IT
Proces
implementa7on
Test
business
IT
Opera7ons
Sales/Ops
Agile TeamProduct Owner
STATER
AGILE
IMPLEMENTATIE
“BIZDEVOPS” TEAMS

31. Agile Portfolio Management
31

32. Where are we now?
32
§ 26 Agile teams up and running
§ Agile portfolio proces in place
§ Time to market 3-4 months
§ Mid Office, Back Office and Interfaces in
CD pipeline
70%
30%
40%
20%
40%

33. The challenges we took on…
§ Resistance
§ This does not work here
§ We can do this ourselves
§ We are front runners in test automation
§ Paradigm shift
§ Waterfall -> Agile
§ People in waterfall project teams
§ Resource issues
§ Product owner

34. Learn more about XebiaLabs

35. Questions?
Type them in now using your control panel or reach out to us directly anytime.
Ton Kueter
https://www.linkedin.com/ton-
kueter-2386482
Andrew Phillips
https://www.linkedin.com/pub/
andrew-phillips/31/911/49b

36.
Thank
You!