The continuous culture 22

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 1

The continuous cultureHow continuous delivery will change the DNA of your company


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


The continuous cultureIt’s a small world afterall


CD is trending

Technology radar 2016, thoughtworks


Why do continuous delivery?

From: cd trends in financial services, CA, 2017


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


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


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.nl

IT complexityFailure at scale


Software development is at least complex


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


IT waste64% of functionality is never or rarely used


First mover vs. Fast follower47% failure vs. 8% failure


Managing costs under complexity


A/B testing: adding a trust certificate

13% increase


A/B testing: adding a video

439% increase


A/B testing: overselling

115% increase


A/B testing: anonymous oneliner testimonials

34% sales increase


Walt Disney

“A giant mouse on the screen would terrifywomen. It’ll never work.”

MGM studios, 1927



Going faster


Change is coming faster


We need to speed up

From: First, break IT, Mulesoft


And we’re going slower



The continuouscultureTime to sustainably deliver

value


Complex problems are explored


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



Design by exploration: continuous delivery

Design

FeedbackMetrics


To satisfy the customer through early and continuous delivery of valuable softwareAgile manifesto


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

Kurt Bittner, Forrester



Adopting a continuousculture


Stop planning, sizing, andestimating


Stop planning


And personal planning


No more red smileys or progress bars


Or red sprints


Report value


Continuous flow


Start looking at results

Complexity:

Lines of code / Cyclomatic

complexity

Adaptability:

Test coverage

Speed of delivery:

Story points


B(us)(iz)DevOps


Business IT patterns

Detailed proposition

Fallback

Manual Acceptance Testing

Education for users

Documentation

Communication

@kimvanwilgen42


It’s not an IT party anymore


Talk about value


Learning organisation


Growth mindset


Discover together and celebrate new knowledgeLearn to explore



Continuous learningPeer learning


Developer cultureIs more than pingpong

PINGPONG AND NERF GUNS


Provide continuousfeedback


Auditing

No more code audits

Everything in version control

Testset change approvals

Enforced peer reviews

Green goes to production

Approvals in workflow


Issue tracking


Build status


Accessible dashboardsFunctionality usage and performance


Kanban provides feedback


Static analysis

@kimvanwilgen58


ContractsVendors, customers and partners


No dependencies

Loosely coupled

Low entry and exit barriers

Less contract negotiation

More collaboration


Enablement, empowerment and partnership



ConclusionGartner Bimodal IT


Learning, innovating and creating

PINGPONG AND NERF GUNS


Be a high performerGo all-in

Date post:	21-Apr-2017
Category:	Engineering
Upload:	kim-van-wilgen
View:	170 times
Download:	1 times

The continuous culture 22

Engineering