continuous delivery nl.linkedin.com/kimvanwilgen · Continuously delivering continuous delivery @kimvanwilgen | Microservices are the first architectural style to fully embrace continuous

Continously delivering

continuous deliveryKim van Wilgen | Schuberg Philis

nl.linkedin.com/kimvanwilgen

[email protected]

www.kimvanwilgen.com

@kimvanwilgen

@kimvanwilgen | www.kimvanwilgen.comContinuously delivering continuous delivery

Customer director Schuberg Philis20

18

Head of software development ANVA

2017

Head of IT KlaverbladVerzekeringen

2014

Hello world1980

Schuberg Philis

3

Mission criticaldigital transformations

Financiallyindependent

Started in2001

300team members (Dec 2018)

EUR 60mrevenue

Market Quality leaderin Business Critical IT Outsourcing

Single KPI100% customer satisfaction

Our customers

4

5


The value of continuous delivery

AGILEDefine and develop incremental customer value

CDDeliver incremental customer value


Go faster!

Go faster


Small things are easier to handle

Large projects 10% success

52% challenged

Small projects74% success

22% challenged


Hypothesis driven development

Unused featuresLarge deliveries 64%Small deliveries 14%


Eliminate waste


Enhance value through early delivery


Constant change

Continuous Delivery (CD) is a set of practices and principles in software engineering aimed at building, testing and releasing software faster and more frequently. They 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

Continuous Delivery (CD) is a set of practices and principles in software engineering aimed at building, testing and releasing software faster and more frequently. They 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


Organize for incremental change

Automation of deployments

Automation of tests

Independent development and delivery

Pervasive visibility of usage and health

Manage the stakeholders

Reducing time, cost and risk


1: Organize for incremental change


Continuously delivering CD

Continuous delivery means you’re building software. So treat is as a

software development process



Grow together consistently and allow time to adjust


Autonomy, self organization and T shaped people


Team autonomy asks leaders to change


2: Automation of deployments


Level 1

Dev Test 1 Test n

Integration Acceptance Production

Dev Test 1 Test n

For each component

Full landscape

Integration automatic

Integration manual

Acceptance Production

Add tests and metrics

Add monitoring

Add reviews


Peer reviews


Review small increments


Monitoring


Static code analysis


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

Improve and maturize contextual


3: Automation of tests



Testing requires architecture, design and prioritization


Testing pyramid

Unit tests are fast and are the test architecture fundament.

01

01

02

0304

High-value tests- Fast (API tests)

- Flaky code- Business critical processes

- Under development

Monitoring in production- Slow tests

- Expensive tests- Externally impacted

01

02

03Lower value tests

- Long-running tests- Stable code

04


Externally impacted functions


Maintainable tests


Infrastructure as code

Version controlTest automation

Configuration tests

Collaborate withthe business

They know their domain, you know test

design.

Grow assurance and enable speed by

shifting left

Mindset

Testers can learn about structure, architecture, maintainability and performance.

Developers can learn the “What would happen if I...” perspective.


Test if there are tests

@kimvanwilgen | www.kimvanwilgen.comThe continuous culture

Build status


Mutation testing


4: Independent deployment and delivery



Branching is your new mother-in-law. Don’t go there unless you’re forced.

Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Martin Fowler, Thoughtworks

Branching means you’re extending integrationFeature pipelines mean you’re extending integration


Isolation and integration


Deployment != releasing

“EVERYTHING FACEBOOK WILL BE RELEASING NEXT YEARIS ALREADY IN PRODUCTION”

- Jez Humble -


Integration pyramid

Business co-creation01

02

03

0405

Inaccessible functionality

Branching

01

02

03 Use toggles

04

Blue / Green05


Coordinate your deployments

At first. And break dependencies.


Acceptance Rehearsal CanaryFull

production

Release strategy

Product owner


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 applicationNeal Ford, Thoughtworks


5: Pervasive visibility of usage and health



Design for data and integrate it in your development


Make logging, static analysis and scans and checks relevant

Adapt to your needs


Build pipelineInsight in process, status and workflow management


Issue tracking


Benefit tracking as part of your solutions

A) Business model definition (Responsibility Argenta)

Customer journey improvement Describe the benefit in the customer journey when the feature is delivered. State the key benefits for the user when the objective of the feature is delivered.

Benefit tracking How will the benefits be tracked to validate the business case?

Non functionals State aspects of security, compliance, audit, SLA and support in case they are different then standard. State regulatory deadline if applicable

Key users State the users of the idea

Key risks State the key risks and mitigating measures.

Pre-approvals [] Compliance [] Security [] Legal & Risk [] Monthly recurring cost

Revenue What is the expected revenue that follows from achieving the goal of the feature

Feature refinement by SBP & BD (YT) in cooperation with Argenta


6: Manage the stakeholders

VS



Speed of delivery isn’t the answer to life, the universe and everything


Don’t get hurt speeding up

Integration of security in your pipeline

Don’t get hurt speeding up


X“If you are doing DevOps without security, you are doing it wrong”

Thiago de Faria – Head of solutions engineering, LINKIT


Shift left on security

VS


Automate first

• SAST

• DAST

• Proxy tools

• Dependency checks

• Custom scripts

Integration in the pipelines


Canary releasing

Cocreating tests

Walkthroughs

Embedded user assistance and

chatbots

Release notes integrated in

deployment

Fallback plans

Manual Acceptance Testing

Education for users

User documentation

Communication about releases

Release process


Releasenotes from jira


Auditing and compliance

Only green to production4 eyes principle

Test and code qualityEverything in version control

Audit and compliance



Customers don’t want continuousdelivery


Legacy code and broken trust


Explain yourgoal

Pull, not pushFirst improve,

then accelarate


Organize for incremental change

Automation of deployments

Automation of tests

Independent development and

delivery

Pervasive visibility of usage and

health

Manage the stakeholders

Reducing time, cost and risk

• www.kimvanwilgen.com

• @kimvanwilgen

• [email protected]

REFERENCES AND QUESTIONS

Documents

continuous delivery nl.linkedin.com/kimvanwilgen · Continuously delivering continuous delivery @kimvanwilgen | Microservices are the first architectural style to fully embrace continuous