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.7k
"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
[XP Keynote] AI for teams: State of play for AI assistance beyond code
birgitta410
0
130
The role of developer skills in today's AI-assisted world
birgitta410
0
170
Cultivating Architecture (2022)
birgitta410
0
460
Redefining confidence: Cognitive biases in an architect's life
birgitta410
0
280
Cultivating Architecture with Principles
birgitta410
1
440
Cultivating Architecture
birgitta410
0
2.2k
To pair, or not to pair
birgitta410
1
480
To pair, or not to pair
birgitta410
0
460
Born for IT? How the image of software developers came about
birgitta410
0
430
Other Decks in Technology
See All in Technology
Generative AI Japan 第一回生成AI実践研究会「AI駆動開発の現在地──ブレイクスルーの鍵を握るのはデータ領域」
shisyu_gaku
0
330
RSCの時代にReactとフレームワークの境界を探る
uhyo
11
3.5k
【NoMapsTECH 2025】AI Edge Computing Workshop
akit37
0
230
AIエージェント開発用SDKとローカルLLMをLINE Botと組み合わせてみた / LINEを使ったLT大会 #14
you
PRO
0
130
サラリーマンの小遣いで作るtoCサービス - Cloudflare Workersでスケールする開発戦略
shinaps
2
470
slog.Handlerのよくある実装ミス
sakiengineer
4
480
Autonomous Database - Dedicated 技術詳細 / adb-d_technical_detail_jp
oracle4engineer
PRO
4
10k
Oracle Cloud Infrastructure IaaS 新機能アップデート 2025/06 - 2025/08
oracle4engineer
PRO
0
110
S3アクセス制御の設計ポイント
tommy0124
3
210
新アイテムをどう使っていくか?みんなであーだこーだ言ってみよう / 20250911-rpi-jam-tokyo
akkiesoft
0
350
20250912_RPALT_データを集める→とっ散らかる問題_Obsidian紹介
ratsbane666
0
100
Apache Spark もくもく会
taka_aki
0
140
Featured
See All Featured
Statistics for Hackers
jakevdp
799
220k
Keith and Marios Guide to Fast Websites
keithpitt
411
22k
GraphQLとの向き合い方2022年版
quramy
49
14k
Large-scale JavaScript Application Architecture
addyosmani
513
110k
A Modern Web Designer's Workflow
chriscoyier
696
190k
Into the Great Unknown - MozCon
thekraken
40
2k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
667
120k
Dealing with People You Can't Stand - Big Design 2015
cassininazir
367
27k
Visualization
eitanlees
148
16k
YesSQL, Process and Tooling at Scale
rocio
173
14k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
23
1.4k
Connecting the Dots Between Site Speed, User Experience & Your Business [WebExpo 2025]
tammyeverts
8
530
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