Sander Hoogendoorn is an independent software architect, agile coach, and programmer. The document discusses trends in software development such as smaller teams, microservices, serverless computing, and continuous delivery in order to deliver value to customers more quickly. It also addresses challenges with scaling agile and ensuring autonomous teams through minimal rules and processes.
%+27788225528 love spells in Huntington Beach Psychic Readings, Attraction sp...
W-JAX 2017 Keynote. It's a small world after all. How thinking small is changing software development big time
1. It’s a small world
after all
Sander Hoogendoorn
ditisagile.nl
Mentoring ▪ Consulting ▪ Training
Agile ▪ Software architecture ▪ Code
@aahoogendoorn
2. Sander Hoogendoorn
Independent dad, software architect,
agile coach, programmer, speaker, writer
CTO ANVA
Former CTO insurance company
Former global agile thoughtleader
Capgemini
sanderhoogendoorn.com
aahoogendoorn
aahoogendoorn
sander@ditisagile.nl
Next
9. The IBM Personal
Computer 5150
The simplest configuration has 16K on-
board RAM and uses an audio cassette to
load and save data. A floppy drive is
optional. A hard drive was not supported.
A system for home or school with a
memory of 64K bytes, a single diskette
drive and its own display, was priced
around $3,000.
Buy now
10. Amazon EC2
Then, in 2006, Amazon launched its
Elastic Compute cloud (EC2) as a
commercial web service that allows
small companies and individuals to rent
computers on which to run their own
computer applications.
Hallo
40. @aahoogendoorn | www.ditisagile.nlIt’s a small word after all 62
To satisfy the customer through early and
continuous delivery of valuable software
Agile manifesto
42. @aahoogendoorn | www.ditisagile.nlIt’s a small word after all 64
Continuous delivery
An approach in which teams ensure that every change to
the system is releasable, and that we can release any
version at the push of a button.
Aimed to make releases boring, so we can deliver
frequently and get fast feedback on what users care about.Jez Humble
58. Team is a pool of people with all the right skills
Often with a ‘technical leader’
Single backlog of small work items
Kanban style board
Small teams form and disband dynamically to
implement epics
Often two to three members
Let the team decide
Product owner becomes an analyst
As little estimates as possible
Stand-ups with whole team
Retrospective on request
Micro-teams
Next
64. @aahoogendoorn | www.ditisagile.nlIt’s a small word after all 104
Lunde’s Law
Given sufficient time any group of
programmers will decide to rewrite
the code.Ron Lunde
65. @aahoogendoorn | www.ditisagile.nlIt’s a small word after all 105
Microservices
In short, the microservice architectural style is an approach
to developing a single application as a suite of small services,
each running in its own process and communicating with
lightweight mechanisms, often an HTTP resource API.
These services are built around business capabilities and
independently deployable by fully automated deployment
machinery. There is a bare minimum of centralized management
of these services, which may be written in different programming
languages and use different data storage technologies.
Martin Fowler
68. @aahoogendoorn | www.ditisagile.nlIt’s a small word after all 109
Distributed systems
Oh and by the way… Doing microservices
(or serverless computing) means that you
are building distributed systemsMe
76. @aahoogendoorn | www.ditisagile.nlIt’s a small word after all 139
@aahoogendoorn | www.ditisagile.nl
References
and questions
www.sanderhoogendoorn.com
www.ditisagile.nl
aahoogendoorn
aahoogendoorn
sander@ditisagile.nl