20170511 the continuous culture sdd

@kimvanwilgen | www.kimvanwilgen.nlThe continuous culture 1
The continuous culture

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

The continuous culture

@kimvanwilgen | www.kimvanwilgen.nl
Going faster

Change is coming faster

We need to speed up
From: First, break IT, Mulesoft

The growth of generic manufacturers and
distributors 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 organizing
business are emerging almost daily.Gerald F. Davis
The vanishing American
corporation

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

IT complexity
Failure at scale

“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

A/B testing: adding a trust certificate
13% increase

A/B testing: overselling
115% increase

Project failure

The continuous
culture
Time to sustainably deliver
value

Software development is at least complex

Managing costs under complexity

Complex problems are explored

Complex problems are continuously explored
There is no end to trying and learning

Innovation is not an epiphany, it’s exploration

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

Small projects vs. Large projects
From: the Chaos manifesto 2013, The Standish group

Adopting a
continuous
culture

Learning organisation

Growth mindset

Discover together and celebrate new knowledge
Learn to explore

Continuous learning
Peer learning, learning on the job

Developer culture
Is more than pingpong

Shorter cycles

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

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 delivering
changes, and ultimately value, to customers by allowing for
more incremental changes to applications in production.
Wikipedia, 2017

Shopping list for
continuous delivery
Continuous integration
Agile way of working
Build pipelines
Code review
Quality metrics
Automated testing
Provisioning / containerization
Issue tracking
Monitoring

Build status

Issue tracking

Accessible dashboards
Functionality usage and performance

Static analysis
@kimvanwilgen49

Peer reviews

Continuous flow

Stop planning

No more red smileys or progress bars

Or red sprints

Knowing value, priority and timelines

Product board
Product board
From: Henrik Kniberg, agile development in a nutshell

Start looking at results
Antipatterns
• Complexity through LOC or
cyclomatic complexity
• Adaptability through test
coverage
• Speed of delivery through
story points

HRM planning should match the continuous flow
Incentives for year results can frustrate business value delivery
To do
MongoDB
university -
DBA
Improve
written
communicatio
n
In
progres
s
Improve
incidents and
problems
process
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
*Huidigfunctieprofiel
OntwikkelenSolide basis
Vakkundig Toekomstbestendig

Agile product
development

Product vision and concept details

Product vision in an hour

Imovators

No dependencies
Loosely coupled
Low entry and exit barriers
Less contract negotiation
More collaboration

Enablement, empowerment and partnership

Autonomous teams

DevOps
Testers: DevTests
Analists: AnalDevTests
Business: BizDevOps
Security: DevOpsSecs
B(us)(iz)Dev(Sec)Ops

DevOps

It’s not an IT party anymore

Talk about value

Business IT antipatterns
Fallback plans
Manual Acceptance Testing
Education for users
User documentation
Communication about
releases
@kimvanwilgen73

Build-in user support and interaction

Auditing
No more code audits
Everything in version control
Testset change approvals
Enforced peer reviews
Green goes to production
Approvals in workflow

Regulatory conformity by design

Conclusion
Continuous culture to enable
the exploration of value

20170511 the continuous culture sdd

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to 20170511 the continuous culture sdd

Similar to 20170511 the continuous culture sdd (20)

Recently uploaded

Recently uploaded (20)

20170511 the continuous culture sdd