20171030 (tdc) continuously delivering continuous delivery

@kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 1
@kimvanwilgen | www.kimvanwilgen.com
Continuously
delivering
continuous
delivery
Kim van Wilgen
www.kimvanwilgen.com

Kim van Wilgen
Head of Software development at ANVA
Former head of IT at Klaverblad
Business background
Managing since 2005
@kimvanwilgen
nl.linkedin.com/kimvanwilgen
kimvanwilgen@gmail.com

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 4
Continuous Delivery (CD) is a set of practices and principles
in software engineering aimed at, building, testing, and
releasing software, faster and more frequently. These
principles help reduce the cost, time and risk of delivering
changes, and ultimately value, to customers by allowing
for more incremental changes to applications in production.
Wikipedia, 2017

Build up value and reduce risk
The value of incremental change

Small projects vs. Large projects
From: the Chaos manifesto 2013, The Standish group

Feedback and data grow value and innovation
The value of incremental change

Building the right thing
Having 14% vs 64% unused features

What is continuous
Klaverblad
ANVA ANVA
Klaverblad Amazon

Tool focused
No
requirements or
product vision
Distributed over
teams
Besides other
projects
So let’s go

Results
Incomplete tests
No shipping choice
No monitoring
No compliance or control

Continuous delivery means you’re
building software. So treat is as a software
development process
Lesson #1

Backlog and prioritizing items

Level 1
Dev Staging Test
Integration Acceptance Production
Dev Staging Test
For each component
Full landscapeDev Staging Test Manual
Dev Staging Test Manual
Integration
Scenario /
UI testing
Acceptance Production
Add tests and metrics
Add monitoring
Add reviews

Improve and maturize
Testing
Security
Performance
Mutation
Experimenting
A/B testing
Canary releasing
Blue / green
deployments
Data driven
decisions
Releasing
Walkthroughs
Chatbots
Distributed
releasing
Health
Issue tracking
Build status
Monitoring
Immutable
servers

Build pipeline
Insight in process, status and workflow management

Monitoring
Instant response and proactive support

Static analysis
Knowing quality
@kimvanwilgen24

Peer reviews

You’re not the only one who’s process is
changing
Lesson #2

Auditing
No more code audits
Everything in version
control
Mutation testing / test
change approvals
Enforced peer reviews
Green goes to production
Approvals in workflow

Regulatory conformity by design

Business IT antipatterns
Fallback plans
Manual Acceptance
Testing
Education for users
User documentation
Communication about
releases
@kimvanwilgen29

@kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 30
Releasenotes from jira

Agile Product management

Test automation requires architecture and
design
Lesson #3

Test pyramid
Focus on small tests and fast feedback that’s valuable and supports you the most

Business users think about the user interface
perspective. They offer examples on how things
should work rather than what is required. This extra
information must be removed to make key examples
simple to communicate and understand.
Refining the specification

Imperative vs. Declarative language
And being unibiquitous

Collaboration of engineers and testers

Branching is your new mother-in-law:
sometimes you have to go there but you
never want to
Lesson #4

Isolation and integration

Branch,
blue/green
Feature toggling
Direct delivery by having
no frontend
Intensive customer collaboration
and preacceptance
The shipping delay pyramid

Customers don’t want continuous delivery
Lesson #5

Insurance
company
Service
provider
Wholesale
Agents
ANVA
Insurtech company for the Netherlands

Collaborate
with users on
test automation
First improve,
then accelarate
Pull, not push
Explain your
goal
Build trust

Closing down
Keep going

References
and questions
kimvanwilgen
kimvanwilgen@gmail.com

20171030 (tdc) continuously delivering continuous delivery

More Related Content

What's hot (19)

Similar to 20171030 (tdc) continuously delivering continuous delivery (20)

Recently uploaded (20)

20171030 (tdc) continuously delivering continuous delivery