Quentin is the CEO of WiredCraft who has a developer and project manager background. He is responsible for managing the day-to-day operations of the Shanghai office. At UXDX Berlin, Quentin took the stage to discuss test and deploy matters. Continuous delivery relies on tools but even more on culture. To be successful, you need to validate assumptions quickly and cheaply. Track everything, automate everything, continuous optimization and continuous delivery are essential.

1. UXDXWiredcraft June 5, 2018

2. UXDXWiredcraft June 5, 2018
Continuous delivery…
the real deal.

3. UXDXWiredcraft June 5, 2018
About Wiredcraft & myself 4
What sucks 6
What's in store for us 8
Who we are 11
This week 14

4. UXDXWiredcraft June 5, 2018
Some context

5. UXDXWiredcraft June 5, 2018
We work with digital & innovation teams within larger multinational
companies. We help them move at the speed of startups & develop a
product culture.

6. UXDXWiredcraft June 5, 2018
What does it mean?
We’re the team behind the
omnichannel strategies of Walmart,
Nike, Starbucks, Hilton & many
others, in Europe & China.
We ship software solutions
at high velocity...
For tens of millions of users.

7. UXDXWiredcraft June 5, 2018
Quentin Berder
President
I’m the Chief Janitor Officer: I do whatever is
necessary for our our team to ship something the
users want, on time... and alive.

8. UXDXWiredcraft June 5, 2018
Let’s get started

9. UXDXWiredcraft June 5, 2018
CD = building, testing and releasing fast & often.
It relies on tools and processes, but more importantly
culture.
ILLUSTRATION OF INFINITE CYCLE

10. UXDXWiredcraft June 5, 2018
<geeking>

11. UXDXWiredcraft June 5, 2018
Our tools:
— Docker + Kubernetes
— Ansible
— Pipelines
— TravisCI
— SonarQube
— Sentry.io
— ELK & TICK
Don’t worry, YMMV.

12. UXDXWiredcraft June 5, 2018
Docker
Containers make it easier to abstract
runtime environment complexity
(e.g. services dependencies). It is NOT
magical blue powder and comes
at the cost of greater complexity.
We use Kubernetes only when
necessary and maintainable for the
organization (i.e. rarely).
TERMINAL W/
DOCKER CL

13. UXDXWiredcraft June 5, 2018
Ansible
Ansible allow us to manage configuration
and automation above and beneath the
containerization layer:
— Host system configuration
— Network configuration
— Cross components orchestration for
deployment
ANSIBLE
LOGO?

14. UXDXWiredcraft June 5, 2018
Pipelines
Pipelines is a lightweight replacement
for Jenkins (mostly because we hate it):
— 2 minutes to setup with pip install
— Easy to configure (yaml)
— Automate triggering of playbooks
— Make accessible to the team
— Auditable log runs
http://github.com/Wiredcraft/pipelines
PIPELINES
LOGO/SCREEN?

15. UXDXWiredcraft June 5, 2018
TravisCI, Sonarqube, Sentry.io...
Continuous Code Quality through automated testing, code quality
analysis and error logging.
SCREENSHOTS
OF THESE 3 APPS

16. UXDXWiredcraft June 5, 2018
ELK, TICK...
Continuous Logging & Monitoring to detect anomalies of deployed builds
and help us investigate the root cause.

17. UXDXWiredcraft June 5, 2018
</geeking>

18. UXDXWiredcraft June 5, 2018
What actually matters:
— Track everything
— Automate everything
— Optimize continuously
— Release continuously
The tools don’t matter that
much.
The goal: develop resilience
& help surface defects early.
If you want to learn more ↓

19. UXDXWiredcraft June 5, 2018
Why should you care?

20. UXDXWiredcraft June 5, 2018
Enable innovation
Nothing beats user validation. No
amount of tech, smart & design.
To compete, you need to be able to
validate your assumptions
quickly, safely & cheaply.
You need tech to be an enabler, not
an obstacle.
ILLUSTRATION

21. UXDXWiredcraft June 5, 2018
So, why is that hard?

22. UXDXWiredcraft June 5, 2018
So, why is that hard?
Culture!

23. UXDXWiredcraft June 5, 2018
Step 0: No product culture
Symptoms:
— IT is defensive & opaque
(e.g. 5 years “digital transformation“ plan)
— Marketing is focused on short term
(e.g. short lived digital campaigns)
Challenge: creating the space for a digital
product culture to be incepted.
ILLUSTRATION
OF EVOLUTION OF
DIGITAL - 1

24. UXDXWiredcraft June 5, 2018
Step 1: Digital Team beta
Symptoms:
— IT is fighting change
(e.g. trying to steal budgets back)
— Marketing is interested but not invested
(e.g. campaigns not tied to business KPIs)
Challenge: the digital product is fragile and
constantly needs to fight to survive.
ILLUSTRATION
OF EVOLUTION OF
DIGITAL - 2

25. UXDXWiredcraft June 5, 2018
Step 2: Some product culture
Symptoms:
— IT is comfortable in a supporting role
(e.g. maintenance, security, ...)
— Marketing owns analytics & com
(e.g. coordinated omni-channel campaigns)
Challenge: the digital team needs to stay lean
and not crumble under the weight of the org.
ILLUSTRATION
OF EVOLUTION OF
DIGITAL - 3

26. UXDXWiredcraft June 5, 2018
Examples of this evolution:
Walmart → Starbucks → Nike

27. UXDXWiredcraft June 5, 2018
What actually matters:
— Have champions at the C-level
— Brace for growing pains
— Do things one step at a time
— Establish clear roles for IT,
marketing & digital
Goal: create a viable digital product
culture that leads on innovation.
If you haven’t started by now, you’re in deep sh*t.
If you want to learn more ↓

28. UXDXWiredcraft June 5, 2018
What have we learned?

29. UXDXWiredcraft June 5, 2018
Let’s wrap it up

30. UXDXWiredcraft June 5, 2018