Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Large projects
10% success
52% challenged
Small projects
74% success
22% challenged
Unused features
Large deliveries 64%
Small deliveries 14%
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Software development is complex
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
@kimvanwilgen | www.kimvanwilgen.com
Constant change
To improve...
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
@kimvanwilgen | www.kimvanwilgen.com
How to deliver
incremental...
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Be able to safely and
sustainably deliver software
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Continuous Delivery (CD) is a set of practices and principles
i...
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
What is continuous?
Naming continuous to be a problem
Amazon
AN...
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
You’re only as small as your MVP
and as agile as your roadmap
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Stop extensive planning
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
And stop red sprints
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Start looking at goals and results
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Product vision and business cases
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
You’re not the only one who’s
process is changing
Auditing and compliance
Everything in version control
Test change approval
Enforced peer reviews
Green goes to production
...
Continuous security
DIY hacking
Integration in the pipeline
Paperless
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Fallback plans
Manual Acceptance Testing
Education for users
Us...
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Reinvent HR, management, roles
and procedures for autonomy
Team autonomy asks
leaders to change
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Autonomy can’t exist without transparancy
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Inspiration over management
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Feedback fun
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
SecDevSecOpsSec
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
“I picked ‘DevOpsDays’ as Dev and Ops
working together because ...
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Learning to learn
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Continuous learning
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Academy, workshops, hackathons, conferences
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Design for fast feedback
and evolution
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Microservices are the first architectural style to fully
embrac...
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Test pyramid reinvented
Small tests and risk based
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Branching is your new mother-in-
law: sometimes you have to go
...
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Branching
Feature flags
No frontend
Co-creation and
pre-accepta...
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Acceptance
by team
Rehearsal
Canary
production
Global
productio...
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Customers don’t want
continuous delivery
8
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Legacy code and broken trust
Explain your
goal
Pull, not push
First improve,
then accelarate
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Continuous
culture
Continuous
delivery
Agile product
developmen...
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
Be ready for surprises
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
@kimvanwilgen | www.kimvanwilgen.com
Closing down
Keep going
@kimvanwilgen | www.kimvanwilgen.comThe continuous culture
@kimvanwilgen | www.kimvanwilgen.com
References
and questions
w...
20180424 / The Lead developer NY / The continuous culture
Upcoming SlideShare
Loading in …5
×

of

20180424 / The Lead developer NY / The continuous culture Slide 1 20180424 / The Lead developer NY / The continuous culture Slide 2 20180424 / The Lead developer NY / The continuous culture Slide 3 20180424 / The Lead developer NY / The continuous culture Slide 4 20180424 / The Lead developer NY / The continuous culture Slide 5 20180424 / The Lead developer NY / The continuous culture Slide 6 20180424 / The Lead developer NY / The continuous culture Slide 7 20180424 / The Lead developer NY / The continuous culture Slide 8 20180424 / The Lead developer NY / The continuous culture Slide 9 20180424 / The Lead developer NY / The continuous culture Slide 10 20180424 / The Lead developer NY / The continuous culture Slide 11 20180424 / The Lead developer NY / The continuous culture Slide 12 20180424 / The Lead developer NY / The continuous culture Slide 13 20180424 / The Lead developer NY / The continuous culture Slide 14 20180424 / The Lead developer NY / The continuous culture Slide 15 20180424 / The Lead developer NY / The continuous culture Slide 16 20180424 / The Lead developer NY / The continuous culture Slide 17 20180424 / The Lead developer NY / The continuous culture Slide 18 20180424 / The Lead developer NY / The continuous culture Slide 19 20180424 / The Lead developer NY / The continuous culture Slide 20 20180424 / The Lead developer NY / The continuous culture Slide 21 20180424 / The Lead developer NY / The continuous culture Slide 22 20180424 / The Lead developer NY / The continuous culture Slide 23 20180424 / The Lead developer NY / The continuous culture Slide 24 20180424 / The Lead developer NY / The continuous culture Slide 25 20180424 / The Lead developer NY / The continuous culture Slide 26 20180424 / The Lead developer NY / The continuous culture Slide 27 20180424 / The Lead developer NY / The continuous culture Slide 28 20180424 / The Lead developer NY / The continuous culture Slide 29 20180424 / The Lead developer NY / The continuous culture Slide 30 20180424 / The Lead developer NY / The continuous culture Slide 31 20180424 / The Lead developer NY / The continuous culture Slide 32 20180424 / The Lead developer NY / The continuous culture Slide 33 20180424 / The Lead developer NY / The continuous culture Slide 34 20180424 / The Lead developer NY / The continuous culture Slide 35 20180424 / The Lead developer NY / The continuous culture Slide 36 20180424 / The Lead developer NY / The continuous culture Slide 37 20180424 / The Lead developer NY / The continuous culture Slide 38 20180424 / The Lead developer NY / The continuous culture Slide 39 20180424 / The Lead developer NY / The continuous culture Slide 40 20180424 / The Lead developer NY / The continuous culture Slide 41 20180424 / The Lead developer NY / The continuous culture Slide 42
Upcoming SlideShare
What to Upload to SlideShare
Next
Download to read offline and view in fullscreen.

1 Like

Share

Download to read offline

20180424 / The Lead developer NY / The continuous culture

Download to read offline

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.

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

20180424 / The Lead developer NY / The continuous culture

  1. 1. Large projects 10% success 52% challenged Small projects 74% success 22% challenged
  2. 2. Unused features Large deliveries 64% Small deliveries 14%
  3. 3. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Software development is complex
  4. 4. @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
  5. 5. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture @kimvanwilgen | www.kimvanwilgen.com How to deliver incremental change In 8 lessons
  6. 6. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Be able to safely and sustainably deliver software
  7. 7. @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
  8. 8. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture What is continuous? Naming continuous to be a problem Amazon ANVAANVA KlaverbladKlaverblad
  9. 9. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture You’re only as small as your MVP and as agile as your roadmap
  10. 10. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Stop extensive planning
  11. 11. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture And stop red sprints
  12. 12. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Start looking at goals and results
  13. 13. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Product vision and business cases
  14. 14. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture You’re not the only one who’s process is changing
  15. 15. Auditing and compliance Everything in version control Test change approval Enforced peer reviews Green goes to production Approvals in workflow Conformity by design
  16. 16. Continuous security DIY hacking Integration in the pipeline Paperless
  17. 17. @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
  18. 18. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Reinvent HR, management, roles and procedures for autonomy
  19. 19. Team autonomy asks leaders to change
  20. 20. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Autonomy can’t exist without transparancy
  21. 21. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture
  22. 22. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Inspiration over management
  23. 23. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Feedback fun
  24. 24. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture SecDevSecOpsSec
  25. 25. @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
  26. 26. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Learning to learn
  27. 27. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Continuous learning
  28. 28. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Academy, workshops, hackathons, conferences
  29. 29. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Design for fast feedback and evolution
  30. 30. @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
  31. 31. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Test pyramid reinvented Small tests and risk based
  32. 32. @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
  33. 33. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Branching Feature flags No frontend Co-creation and pre-acceptance The shipping delay pyramid
  34. 34. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Acceptance by team Rehearsal Canary production Global production Release strategy Feature flags Sustainable pace Shipping delay Impact reduction
  35. 35. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Customers don’t want continuous delivery 8
  36. 36. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Legacy code and broken trust
  37. 37. Explain your goal Pull, not push First improve, then accelarate
  38. 38. @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
  39. 39. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture Be ready for surprises
  40. 40. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture @kimvanwilgen | www.kimvanwilgen.com Closing down Keep going
  41. 41. @kimvanwilgen | www.kimvanwilgen.comThe continuous culture @kimvanwilgen | www.kimvanwilgen.com References and questions www.kimvanwilgen.com kimvanwilgen kimvanwilgen@gmail.com
  • isbkch

    Apr. 25, 2018

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.

Views

Total views

981

On Slideshare

0

From embeds

0

Number of embeds

31

Actions

Downloads

12

Shares

0

Comments

0

Likes

1

×