20170511 the continuous culture sdd

66
@kimvanwilgen | www.kimvanwilgen.nl The continuous culture 1 The continuous culture

Transcript of 20170511 the continuous culture sdd

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 1

The continuous culture

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 2

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

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 3

The continuous culture

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 5

@kimvanwilgen | www.kimvanwilgen.nl

Going faster

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 6

Change is coming faster

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 7

We need to speed up

From: First, break IT, Mulesoft

Fintech disruptors

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 10

The growth of generic manufacturers anddistributors and the widespread availibility of cloud services mean that barriers to entry have collapsed in many industries. Thanks to low barriers to entry, new ways of organizingbusiness are emerging almost daily.Gerald F. Davis

The vanishing American

corporation

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 11

Imitation barriers have collapsed too though…

Failure innovators

47%

Failure imitators

8%

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

@kimvanwilgen | www.ditisagile.nl

Being slower

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 13

IT complexityFailure at scale

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 14

“Have you ever seen what many teenagers teach to parrots? What do you expect? So this was an experiment after all, but about people, or even about the common sense of computer programmers.”

Nello Cristianini,

AI prof at Bristol university

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 15

A/B testing: adding a trust certificate

13% increase

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 17

A/B testing: overselling

115% increase

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 19

Project failure

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 20

@kimvanwilgen | www.kimvanwilgen.nl

The continuouscultureTime to sustainably deliver

value

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 21

Software development is at least complex

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 22

Managing costs under complexity

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 23

Complex problems are explored

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 24

Complex problems are continuously exploredThere is no end to trying and learning

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 26

Innovation is not an epiphany, it’s exploration

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 28

To satisfy the customer through early and continuous delivery of valuable software

Agile manifesto

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 29

Small projects vs. Large projects

From: the Chaos manifesto 2013, The Standish group

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 31

@kimvanwilgen | www.kimvanwilgen.nl

Adopting a continuousculture

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 32

Learning organisation

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 33

Growth mindset

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 34

Discover together and celebrate new knowledgeLearn to explore

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 35

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 36

Continuous learningPeer learning, learning on the job

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 37

Developer cultureIs more than pingpong

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 38

Shorter cycles

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 39

If agile was the opening act, continuous delivery is the headliner.

Kurt Bittner, Forrester

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 40

Why do continuous delivery?

From: cd trends in financial services, CA, 2017

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 41

Continuous delivery is a DevOps software development practice where code changes are automatically built, tested, and prepared for a release to production.Amazon web services

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 42

The term "Continuous Delivery" ("CD") represents a set of principles and practices in growing use in software development to improve the process of software delivery. Techniques such as automated testing, continuous integration and automated deployments allow software to be developed to a high standard and easily packaged and deployed to test environments, resulting in the ability to rapidly, reliably and repeatedly push out enhancements and bug fixes to customers at low risk and with minimal manual overhead.

Wikipedia, 2011

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 43

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

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 44

Shopping list forcontinuous delivery

Continuous integration

Agile way of working

Build pipelines

Code review

Quality metrics

Automated testing

Provisioning / containerization

Issue tracking

Monitoring

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 45

Build status

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 46

Issue tracking

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 48

Accessible dashboardsFunctionality usage and performance

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 49

Static analysis

@kimvanwilgen49

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 50

Peer reviews

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 51

Continuous flow

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 53

Stop planning

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 54

No more red smileys or progress bars

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 55

Or red sprints

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 56

Knowing value, priority and timelines

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 57

Product board

Product board

From: Henrik Kniberg, agile development in a nutshell

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 59

Start looking at results

Antipatterns

• Complexity through LOC or

cyclomatic complexity

• Adaptability through test

coverage

• Speed of delivery through

story points

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 61

HRM planning should match the continuous flowIncentives for year results can frustrate business value delivery

To do

MongoDBuniversity -

DBA

Improvewritten

communication

In progres

s

Improveincidents and

problemsprocess

Done

OCE Java exam

OCE Java study ch. 8

OCE Java study ch. 7

10

● Kwaliteit

9 ● Oplossingsgericht ● Betrouwbaarheid

● Functionele kennis ● Focus ● Samenwerking

8 ● Toegangkelijkheid

● Vaardigheden ● Zelfstandigheid

7 ● Openheid

● Zelfinitiatief ● Klant centraal ● Innovatief

6 ● Meedenkend ● Communicatief

5 ● Kennisdeling

● Rapporteren ● Technische kennis

4 ● Lef

● TestComplete ● Specialiteit

3

● Junit

2

1

0 1 2 3 4 5 6 7 8 9 10

* H

uid

ig f

un

ctie

pro

fiel

OntwikkelenSolide basis

Vakkundig Toekomstbestendig

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 62

Agile product development

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 63

Product vision and concept details

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 64

Product vision in an hour

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 65

Imovators

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 66

No dependencies

Loosely coupled

Low entry and exit barriers

Less contract negotiation

More collaboration

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 67

Enablement, empowerment and partnership

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 68

Autonomous teams

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 69

DevOps

Testers: DevTests

Analists: AnalDevTests

Business: BizDevOps

Security: DevOpsSecs

B(us)(iz)Dev(Sec)Ops

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 70

DevOps

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 71

It’s not an IT party anymore

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 72

Talk about value

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 73

Business IT antipatterns

Fallback plans

Manual Acceptance Testing

Education for users

User documentation

Communication about

releases

@kimvanwilgen73

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 74

Build-in user support and interaction

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 75

Auditing

No more code audits

Everything in version control

Testset change approvals

Enforced peer reviews

Green goes to production

Approvals in workflow

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 76

Regulatory conformity by design

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 78

@kimvanwilgen | www.kimvanwilgen.nl

ConclusionContinuous culture to enable

the exploration of value