This document discusses continuous delivery and the benefits of adopting a continuous culture in software development. It advocates for practices like continuous integration, automated testing and deployments to allow for rapid and reliable software releases. Adopting these principles can help reduce costs and risks while delivering more value to customers. The document also provides tips for organizations looking to transition to a continuous delivery model, such as focusing on results and value over plans, establishing a learning culture, and providing continuous feedback.
2. @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
kimvanwilgen@gmail.com
www.kimvanwilgen.com
About me
6. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 6
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
7. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 7
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
8. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 8
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
11. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 11
IT success stats
• 25% failure
• 20% to 25% negative ROI
• 50% material rework
“Improving IT Project Outcomes by
Systematically Managing and Hedging Risk.”
IDC, D. Wiklund and J.C. Pucciarelli, 2009.
Project failure
Failure
Negative
ROI
Major
changes
IT PROJECT RESULTS
19. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 19
Walt Disney
“A giant mouse on the screen would terrify
women. It’ll never work.”
MGM studios, 1927
24. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 24
@kimvanwilgen | www.kimvanwilgen.nl
The continuous
culture
Time to sustainably deliver
value
29. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 29
To satisfy the customer through early and
continuous delivery of valuable software
Agile manifesto
30. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 30
If agile was the opening act,
continuous delivery is the headliner.
Kurt Bittner, Forrester
51. @kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 52
Auditing
No more code audits
Everything in version control
Testset change approvals
Enforced peer reviews
Green goes to production
Approvals in workflow