These are my slides for my talk at The Lead Developer New York on The continuous culture. How to implement an experimental culture across the organisation, allowing small experiments and incremental change to seek real value.

2. Large projects
10% success
52% challenged
Small projects
74% success
22% challenged

3. Unused features
Large deliveries 64%
Small deliveries 14%

4. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Software development is complex

5. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
@kimvanwilgen | www.kimvanwilgen.com
Constant change
To improve is to change.
Being perfect is to change
often.
Winsten Churchill

6. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
@kimvanwilgen | www.kimvanwilgen.com
How to deliver
incremental
change
In 8 lessons

7. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Be able to safely and
sustainably deliver software

8. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
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

9. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
What is continuous?
Naming continuous to be a problem
Amazon
ANVAANVA
KlaverbladKlaverblad

10. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
You’re only as small as your MVP
and as agile as your roadmap

11. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Stop extensive planning

12. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
And stop red sprints

13. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Start looking at goals and results

14. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Product vision and business cases

15. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
You’re not the only one who’s
process is changing

16. Auditing and compliance
Everything in version control
Test change approval
Enforced peer reviews
Green goes to production
Approvals in workflow
Conformity by design

17. Continuous security
DIY hacking
Integration in the pipeline
Paperless

18. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Fallback plans
Manual Acceptance Testing
Education for users
User documentation
Communication about releases
Canary releasing
Cocreating tests
Walkthroughs
Embedded user assistance and chatbots
Release notes integrated in deployment
Business IT antipatterns
@kimvanwilgen39

19. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Reinvent HR, management, roles
and procedures for autonomy

20. Team autonomy asks
leaders to change

21. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Autonomy can’t exist without transparancy

22. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture

23. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Inspiration over management

24. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Feedback fun

25. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
SecDevSecOpsSec

26. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
“I picked ‘DevOpsDays’ as Dev and Ops
working together because ‘Agile System
Administration’ was too long,” he said.
“There never was a grand plan for DevOps
as a word.”Patrick Debois
Founder of Devops

27. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Learning to learn

28. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Continuous learning

29. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Academy, workshops, hackathons, conferences

30. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Design for fast feedback
and evolution

31. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
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

32. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Test pyramid reinvented
Small tests and risk based

33. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Branching is your new mother-in-
law: sometimes you have to go
there but you want to minimize it

34. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Branching
Feature flags
No frontend
Co-creation and
pre-acceptance
The shipping delay pyramid

35. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Acceptance
by team
Rehearsal
Canary
production
Global
production
Release strategy
Feature flags
Sustainable pace
Shipping delay
Impact reduction

36. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Customers don’t want
continuous delivery
8

37. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Legacy code and broken trust

38. Explain your
goal
Pull, not push
First improve,
then accelarate

39. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
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

40. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Be ready for surprises

41. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
@kimvanwilgen | www.kimvanwilgen.com
Closing down
Keep going

42. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
@kimvanwilgen | www.kimvanwilgen.com
References
and questions
www.kimvanwilgen.com
kimvanwilgen
kimvanwilgen@gmail.com