Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
"We're Agile, we don't do documentation"
Search
Birgitta Boeckeler
June 09, 2017
Technology
1
1.5k
"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
Cultivating Architecture (2022)
birgitta410
0
370
Redefining confidence: Cognitive biases in an architect's life
birgitta410
0
220
Cultivating Architecture with Principles
birgitta410
1
340
Cultivating Architecture
birgitta410
0
2.1k
To pair, or not to pair
birgitta410
1
430
To pair, or not to pair
birgitta410
0
400
Born for IT? How the image of software developers came about
birgitta410
0
260
Building Offline Webapps
birgitta410
0
99
Other Decks in Technology
See All in Technology
ことばをそろえる / Bridging the Terminology Gap
amaotone
5
1k
実践ジオフェンス 効率的に開発するために
navitimejapan
PRO
2
130
日経電子版から始まった内製開発の現在地と向き合っている課題/inhouse
nishiuma
0
230
GraphQLとスキーマファーストで切り開く ライドシェアの未来
ku0522a
0
490
Dojo 20240830 COBOL to Java on Z
ichikawayasuhisa
0
240
エンジニア採用を起点に取り組む組織の改善活動と課題、中長期のタスク管理/ #HRmethod
nishiuma
4
3.3k
New Relicで実践する外形監視
aeonpeople
1
120
Azure SQL Database Hyperscale HA レプリカの監視
sansantech
PRO
0
190
AWS IAM Identity Center議論会 〜 認証認可結合モデルと認証認可分離モデル / 20240827-jawsug-arch-iam_identity_center
opelab
3
320
20分で分かるIAM全機能 (拡大版) / 20240903-jawsug-yokohama-iam
opelab
3
120
Oracle Database Backup Service:サービス概要のご紹介
oracle4engineer
PRO
0
4k
LLMに日本語テキストを学習させる意義
ksaito
13
3.4k
Featured
See All Featured
Principles of Awesome APIs and How to Build Them.
keavy
125
16k
Happy Clients
brianwarren
96
6.6k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
28
2.2k
Documentation Writing (for coders)
carmenintech
65
4.3k
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
103
47k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
662
120k
Gamification - CAS2011
davidbonilla
79
4.9k
Facilitating Awesome Meetings
lara
49
5.9k
It's Worth the Effort
3n
182
27k
Building a Scalable Design System with Sketch
lauravandoore
458
32k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
157
15k
How to Ace a Technical Interview
jacobian
275
23k
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