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
200
Cultivating Architecture (2022)
birgitta410
0
460
Redefining confidence: Cognitive biases in an architect's life
birgitta410
0
290
Cultivating Architecture with Principles
birgitta410
1
440
Cultivating Architecture
birgitta410
0
2.3k
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
440
Other Decks in Technology
See All in Technology
OTEPsで知るOpenTelemetryの未来 / Observability Conference Tokyo 2025
arthur1
0
320
abema-trace-sampling-observability-cost-optimization
tetsuya28
0
360
webpack依存からの脱却!快適フロントエンド開発をViteで実現する #vuefes
bengo4com
4
3.7k
AIでデータ活用を加速させる取り組み / Leveraging AI to accelerate data utilization
okiyuki99
5
1.4k
アウトプットから始めるOSSコントリビューション 〜eslint-plugin-vueの場合〜 #vuefes
bengo4com
3
1.8k
生成AI時代のPythonセキュリティとガバナンス
abenben
0
150
頭部ふわふわ浄酔器
uyupun
0
240
マルチエージェントのチームビルディング_2025-10-25
shinoyamada
0
210
QA業務を変える(!?)AIを併用した不具合分析の実践
ma2ri
0
160
Okta Identity Governanceで実現する最小権限の原則
demaecan
0
190
JSConf JPのwebsiteをGatsbyからNext.jsに移行した話 - Next.jsの多言語静的サイトと課題
leko
2
190
SRE × マネジメントレイヤーが挑戦した組織・会社のオブザーバビリティ改革 ― ビジネス価値と信頼性を両立するリアルな挑戦
coconala_engineer
0
290
Featured
See All Featured
Save Time (by Creating Custom Rails Generators)
garrettdimon
PRO
32
1.7k
Exploring the Power of Turbo Streams & Action Cable | RailsConf2023
kevinliebholz
36
6.1k
Balancing Empowerment & Direction
lara
5
700
Why You Should Never Use an ORM
jnunemaker
PRO
59
9.6k
Code Reviewing Like a Champion
maltzj
526
40k
Making the Leap to Tech Lead
cromwellryan
135
9.6k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
31
2.7k
Raft: Consensus for Rubyists
vanstee
140
7.2k
Designing for Performance
lara
610
69k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
9
930
Six Lessons from altMBA
skipperchong
29
4k
Practical Orchestrator
shlominoach
190
11k
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