20171116 (buildstuff) the continuous culture

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 1
The continuous culture

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
www.kimvanwilgen.com
About me

The continuous culture

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

@aahoogendoorn | www.ditisagile.nlDesigning, developing, testing and deploying microservices 5
@kimvanwilgen | www.ditisagile.nl
Going faster
Keeping up with competition

Software development is complex

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

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

Innovation is not an epiphany, it’s exploration

Flow eliminates waste and overhead

Flow provides insight
Or at least enough of it

@kimvanwilgen | www.kimvanwilgen.nl
How to deliver
incremental
change
In 10 lessons

Be able to safely and
sustainably deliver software to
enable experiments

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

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

@kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 20
@kimvanwilgen | www.kimvanwilgen.com
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

Have a backlog and define your MVP

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

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

You’re only as small as your MVP
and as agile as your roadmap

@kimvanwilgen| www.kimvanwilgen.comContinuously delivering continuous delivery 30
Stop extensive planning

And stop red sprints

Agile Product management

Product vision and business cases

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

Auditing and
compliancce
Everything in version
control
Mutation testing / test
change approvals
Enforced peer reviews
Green goes to production
Approvals in workflow
Conformity by design

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

Releasenotes from jira

Old school HR, management and
functions undermine autonomy.
Reinvent them

Inspiration over management

Feedforward
Integration with each iteration for continuous flow
Stakeholder input
For acceptance and selfcritism
Feedback for
improvement of the team
Supportive feedback
for help with patterns
or goals

Start looking at results

Feedback fun

Autonomy means
trusting and giving space

Team autonomy asks
leaders to change

Learning to learn

Learning cool new stuff everyday

Continuous learning

Discover together and celebrate new knowledge
Learn to explore

Academy, workshops, hackatons, conferences

Design for fast feedback and
evolution

Microservices are the first architectural style to fully
embrace continuous delivery. It is an evolutionary
architecture, which supports incremental non-
breaking change as a first principle along multiple
dimensions at the structural level of the application
Neal Ford, Thoughtworks

Test pyramid
Small tests and risk based

Maintainable tests
And living documentation

Branching is your new mother-in-
law: sometimes you have to go
there but you want to minimize this

Isolation and integration

Branching
Feature toggling
No frontend path
Co-creation and
pre-acceptance
The shipping delay pyramid

Customers don’t want
continuous delivery

Legacy code and broken trust

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

Continuous
culture
Continuous
delivery
Agile product
development
Learning
organisation
Agile HR
Autonomous
teams
Microservices
Enable rapid prototyping
Do small experiments to
seek value
Enable learning
from experiments
Enable an evolutionary
architecture
Empower teams to decide
and adapt fast
Support people to learn
agility and improve in
their capabilities

Be ready for surprises

Closing down
Keep going

References
and questions
www.kimvanwilgen.com
kimvanwilgen
kimvanwilgen@gmail.com

20171116 (buildstuff) the continuous culture

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a 20171116 (buildstuff) the continuous culture

Similar a 20171116 (buildstuff) the continuous culture (20)

Último

Último (20)

20171116 (buildstuff) the continuous culture