20171030 (tdc) continuously delivering continuous delivery

@kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery 1

@kimvanwilgen | www.kimvanwilgen.com

Continuously delivering continuous deliveryKim 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

[email protected]


@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 deliveringchanges, and ultimately value, to customers by allowingfor 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 innovationThe value of incremental change


Building the right thingHaving 14% vs 64% unused features


What is continuous

Klaverblad

ANVA ANVA

Klaverblad Amazon


Tool focusedNo

requirements or product vision

Distributed over teams

Besides other projects

So let’s go



ResultsIncomplete tests

No shipping choice

No monitoring

No compliance or control


Continuous delivery means you’rebuilding software. So treat is as a software development processLesson #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

IntegrationScenario / 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 pipelineInsight in process, status and workflow management


MonitoringInstant response and proactive support


Static analysisKnowing 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 controlMutation testing / test change approvalsEnforced peer reviews Green goes to productionApprovals 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 anddesignLesson #3


Test pyramidFocus 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 thingsshould work rather than what is required. This extra information must be removed to make key examplessimple to communicate and understand.

Refining the specification


Imperative vs. Declarative languageAnd being unibiquitous


Collaboration of engineers and testers


Branching is your new mother-in-law: sometimes you have to go there but younever want toLesson #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 deliveryLesson #5


Insurance company

Service provider

Wholesale

Agents

ANVAInsurtech company for the Netherlands


Collaborate with users on

test automation

First improve, then accelarate

Pull, not pushExplain your

goal

Build trust



Closing downKeep going



References and questions


kimvanwilgen

[email protected]

20171030 (tdc) continuously delivering continuous delivery

Engineering

Transcript of 20171030 (tdc) continuously delivering continuous delivery