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.6k
"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
410
Redefining confidence: Cognitive biases in an architect's life
birgitta410
0
240
Cultivating Architecture with Principles
birgitta410
1
380
Cultivating Architecture
birgitta410
0
2.2k
To pair, or not to pair
birgitta410
1
450
To pair, or not to pair
birgitta410
0
430
Born for IT? How the image of software developers came about
birgitta410
0
340
Building Offline Webapps
birgitta410
0
120
Other Decks in Technology
See All in Technology
トラシューアニマルになろう ~開発者だからこそできる、安定したサービス作りの秘訣~
jacopen
2
2k
OpenID Connect for Identity Assurance の概要と翻訳版のご紹介 / 20250219-BizDay17-OIDC4IDA-Intro
oidfj
0
270
運用しているアプリケーションのDBのリプレイスをやってみた
miura55
1
710
レビューを増やしつつ 高評価維持するテクニック
tsuzuki817
1
710
エンジニアが加速させるプロダクトディスカバリー 〜最速で価値ある機能を見つける方法〜 / product discovery accelerated by engineers
rince
4
320
開発スピードは上がっている…品質はどうする? スピードと品質を両立させるためのプロダクト開発の進め方とは #DevSumi #DevSumiB / Agile And Quality
nihonbuson
2
2.9k
技術負債の「予兆検知」と「状況異変」のススメ / Technology Dept
i35_267
1
1.1k
目の前の仕事と向き合うことで成長できる - 仕事とスキルを広げる / Every little bit counts
soudai
24
7.1k
モノレポ開発のエラー、誰が見る?Datadog で実現する適切なトリアージとエスカレーション
biwashi
6
800
バックエンドエンジニアのためのフロントエンド入門 #devsumiC
panda_program
18
7.5k
7日間でハッキングをはじめる本をはじめてみませんか?_ITエンジニア本大賞2025
nomizone
2
1.8k
Building Products in the LLM Era
ymatsuwitter
10
5.4k
Featured
See All Featured
Optimising Largest Contentful Paint
csswizardry
34
3.1k
The Straight Up "How To Draw Better" Workshop
denniskardys
232
140k
Designing Experiences People Love
moore
140
23k
Navigating Team Friction
lara
183
15k
Imperfection Machines: The Place of Print at Facebook
scottboms
267
13k
How to train your dragon (web standard)
notwaldorf
91
5.8k
The Cost Of JavaScript in 2023
addyosmani
47
7.3k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
174
51k
Faster Mobile Websites
deanohume
306
31k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
33
2.1k
Bash Introduction
62gerente
611
210k
Fireside Chat
paigeccino
34
3.2k
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