Speaker Deck
Speaker Deck Pro
Sign in
Sign up
for free
"We're Agile, we don't do documentation"
Birgitta Boeckeler
June 09, 2017
Technology
1
700
"We're Agile, we don't do documentation"
Slides as presented at "The Lead Developer" conference 2017 in London
Birgitta Boeckeler
June 09, 2017
Tweet
Share
More Decks by Birgitta Boeckeler
See All by Birgitta Boeckeler
birgitta410
0
30
birgitta410
0
86
birgitta410
0
1.4k
birgitta410
1
170
birgitta410
0
130
birgitta410
0
68
birgitta410
0
44
Other Decks in Technology
See All in Technology
sylph01
0
160
viva_tweet_x
4
2.5k
ocise
1
1.3k
ishiayaya
PRO
0
320
layerx
1
700
kurochan
0
530
kentaro
1
320
line_developers
PRO
2
1.2k
clustervr
0
160
shirayanagiryuji
1
400
satotakeshi
0
160
mmarukaw
0
1.4k
Featured
See All Featured
kneath
294
39k
keithpitt
401
20k
dougneiner
55
5.4k
hatefulcrawdad
257
17k
62gerente
587
200k
imathis
478
150k
bkeepers
321
53k
searls
204
35k
addyosmani
494
110k
mojombo
358
62k
malarkey
192
8.5k
zakiwarfel
88
3.3k
Transcript
“WE’RE AGILE, WE DON’T DO DOCUMENTATION” @birgitta410 B i r
g i t t a B ö c k e l e r
None
“Documenting Software Architectures – Views and Beyond” 2nd edition, 2011;
Clements, Bachmann, Bass, Garlan, Ivers, Little, Merson, Nord, Stafford
None
None
None
None
None
None
DESCRIBING SOFTWARE
None
WHERE ARE YOU? 1:1 UML diagrams No documentation at all
“Self- documenting code” Tests are readable specification
PURPOSE of documentation?
For the sake of a PROCESS.
PURPOSE of documentation?
Create a COMMON UNDERSTANDING. 1
None
The wall of COMMON UNDERSTANDING. Containers & Tech Stack Environments
Components … … … Up for grabs!
Surface and understand COMPLEXITY. 2
… … … Data schema migrations Synching behavior … Design
of storage module
INFO GRAPHICS.
“WIDGET” KITS.
Create EMPATHY. 3
Empathy between TECH DECISION MAKERS and developers.
“Working on software without guidance, without documentation, is anxiety-producing” https://medium.com/@duretti/no-flex-zone-empathy-driven-development-aebf4d8cf7cf
Empathy with EACH OTHER.
Empathy between PRODUCT PEOPLE and developers.
Empathy with OTHER TECHNOLOGISTS.
Help our FUTURE SELVES make informed DECISIONS. 4
Architecture DECISION records. http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions “Without understanding the rationale (…), only
two choices: 1. Blindly accept the decision. 2. Blindly change it.”
LIGHTWEIGHT architecture DECISION records. https://github.com/npryce/adr-tools
Describe the PROBLEM, not just the SOLUTION.
CREATIVE problem SOLVING. 5
None
None
None
None
But how do we keep it UP TO DATE?!
@kaeff
As LITTLE as possible. Make it VISIBLE. Include in RITUALS.
Create OWNERSHIP through COLLABORATION.
Help our FUTURE SELVES make informed DECISIONS. Surface and understand
COMPLEXITY. Create COMMON UNDERSTANDING. CREATIVE problem SOLVING. Create EMPATHY.
<> Code THE TRUTH HOW-TOs HISTORY MAPS CREATIVE THINKING
“Individuals and interactions” “Business people and developers work together daily”
“Face to face communication” “Attention to technical excellence and good design” “Simplicity”
@birgitta410