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

[email protected]

www.kimvanwilgen.com

About me


The continuous culture


Insurance company

Service provider

Wholesale

Agents

ANVAInsurtech company for the Netherlands

@aahoogendoorn | www.ditisagile.nlDesigning, developing, testing and deploying microservices 5

@kimvanwilgen | www.ditisagile.nl

Going fasterKeeping 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 innovationThe value of incremental change


Building the right thingHaving 14% vs 64% unused features


Innovation is not an epiphany, it’s exploration


Flow eliminates waste and overheadThe value of incremental change


Flow provides insightOr at least enough of it


@kimvanwilgen | www.kimvanwilgen.nl

How to deliverincrementalchangeIn 10 lessons


Be able to safely andsustainably deliver software toenable 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 deliveringchanges, 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 focusedNo

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

ResultsIncomplete tests

No shipping choice

No monitoring

No compliance or control


Continuous delivery means you’rebuilding 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

IntegrationScenario / 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’sprocess is changing


Auditing andcompliancce

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 andfunctions undermine autonomy. Reinvent them


Inspiration over management


FeedforwardIntegration with each iteration for continuous flow

Stakeholder inputFor acceptance and selfcritism

Feedback forimprovement of the team

Supportive feedback for help with patternsor 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 knowledgeLearn to explore


Academy, workshops, hackatons, conferences


Design for fast feedback andevolution


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 pyramidSmall tests and risk based


Maintainable testsAnd 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 pushExplain your

goal

Build trust


Continuousculture

Continuousdelivery

Agile product development

Learning organisation

Agile HR

Autonomousteams

Microservices

Enable rapid prototyping

Do small experiments toseek value

Enable learningfrom experiments

Enable an evolutionaryarchitecture

Empower teams to decideand adapt fast

Support people to learnagility and improve in their capabilities


Be ready for surprises



Closing downKeep going



References and questions

www.kimvanwilgen.com

kimvanwilgen

[email protected]

20171116 (buildstuff) the continuous culture

Engineering